Skip to content
Rowsafe
Docs

Create a server for me

Rowsafe creates a database server in your own cloud account, protected from the first minute.

No server yet? Rowsafe creates one in your own cloud account, installs the database and protects it from the first minute: continuous backups, Proof and Pulse.

  • Clouds: Hetzner, DigitalOcean, Vultr, AWS, Google Cloud, Azure and OVHcloud.
  • Databases: PostgreSQL, MySQL, MariaDB, Valkey, ClickHouse, OpenSearch, Qdrant or Meilisearch.

It's your server: your cloud bills you, and you can log in to it. Everything else in these docs works on it as on any server.

No cloud account?

Rowsafe Cloud runs the same server in Rowsafe's account, billed by the hour.

What it costs

  • Your cloud bills you directly for the server. Rowsafe adds nothing to that bill.
  • The dashboard shows each size's monthly price before you create anything. Where it says "about" or "from", it's an estimate from list prices. Your cloud's bill is what counts; traffic and taxes can add to it.
  • It counts as one of your plan's servers. Its backups go to Rowsafe Storage and count toward your plan's storage.

Before you start

Create the server

Start

Open Servers, click Add server and choose Create a server for me. Pick the cloud account, or click Connect a cloud account.

Region, size and name

  • Region: the one closest to your app.
  • Server size: the suggested size (the cheapest with 2 CPUs and 4 GB of memory) suits most apps. You can resize later.
  • Server name: lowercase letters, digits and dashes, like shop-db. It's also the database's name in Rowsafe.
  • Database and version: see Databases for versions and limits (MySQL needs Intel or AMD; ClickHouse and OpenSearch need 4 GB of memory, Qdrant 2 GB).
  • Extensions (PostgreSQL, optional): pgvector, PostGIS or TimescaleDB. See Extensions.

Who can connect

Add your app servers' and your own addresses (Add my current IP fills in yours). Leave it empty and nobody can connect until you add some.

SSH access (optional)

Add your SSH public key to log in yourself, and the addresses that may reach SSH. Rowsafe never adds its own key. See SSH.

What Rowsafe may do when you click

The same choices as on any server (what Rowsafe may do). Rowsafe does these only when someone clicks and confirms.

ChoiceStarts
Restart or stop PostgreSQL (Restart, Rewind the whole database)On
Install PostgreSQL updates and upgradesOn
Install the server's security updatesOff
Reboot the serverOff
Change the server's own firewallOff (your cloud's firewall already decides who can connect). On where Rowsafe puts the firewall on the server itself (some OVHcloud projects).
Create PostgreSQL clusters (for a fork or a restored copy on this server)Off

Choose carefully: changing them later needs root on the server, so SSH access.

Create server

Check the summary (size, region, monthly price) and click Create server.

What happens next

It takes about 5 minutes. You can leave the page.

  1. Creating the server. A Debian server (13 where offered, else 12), with a firewall that lets in only your addresses. Everything is tagged rowsafe (rowsafe=1 on AWS).
  2. Starting up. The server runs the Rowsafe installer once, with a one-time token that works only for it.
  3. Installing the database from its project's own packages or release (checked), with TLS and a password or API key, then your extensions and the Rowsafe agent.
  4. Turning on backups to Rowsafe Storage, encrypted on the server.
  5. Ready. Backed up, tested weekly by Proof, watched by Pulse.

If something goes wrong, the page says what, and what was made in your cloud is removed. Click Try again, or Change region or size (for example when a region is out of capacity or you hit your cloud's limit).

Save the backup passphrase

Without the passphrase, no backup can be restored

Backups are encrypted on the server with this passphrase, and Rowsafe doesn't have it. Save it before you rely on the database.

On the server's page, under Save your backup passphrase:

  1. Click Show passphrase.
  2. Copy it into your password manager, outside this server.
  3. Tick I saved it somewhere safe, outside this server.

Until you do, the dashboard reminds you and you can't delete the server.

The passphrase never leaves the server unencrypted: it's encrypted for your browser only, like new database passwords. Only owners and admins can show it (AI agents can't), and each time is in the audit log.

Connect your app

When the server is ready, its page shows Connect your app: the server's address and the port (ports).

  1. Click Create database and user (Valkey: Create a login for your app; Qdrant: Make an API key for your app). The password is made on the server and only you see it. See Databases & users.
  2. Make sure your app's address is under Who can connect.
  3. Connect with TLS: sslmode=require (MySQL and MariaDB: ssl-mode=REQUIRED; Valkey: rediss://; ClickHouse: --secure on 9440, or https:// on 8443).

The certificate is made on the server, not by a public authority, so verify-full refuses it. Clients that check certificates need that turned off (like redis-cli --insecure or curl --insecure). On Rowsafe Cloud, servers get a trusted certificate.

Who can connect

Two locks keep the database private:

  • A firewall: only your addresses reach the database's port. SSH is closed unless you opened it. It's your cloud's firewall, except on new OVHcloud projects, where it's on the server itself.
  • The database itself: network logins need TLS and a password or API key.

Change the addresses on the server's page under Who can connect, then click Save. It applies within seconds. Up to 50 IPv4 or IPv6 addresses or ranges (like 203.0.113.0/24). 0.0.0.0/0 lets anyone try, with a password; the dashboard warns you.

Extensions

On PostgreSQL 15 to 18, pgvector, PostGIS and TimescaleDB (Apache-2.0 edition) are one switch each, as on Rowsafe Cloud:

  • At create time: tick them under Extensions. They're on in every database.
  • Later: turn one on in Databases & users. This needs Install PostgreSQL updates and upgrades allowed. TimescaleDB also needs Restart or stop PostgreSQL: PostgreSQL restarts once, after a Mark.
  • With a standby, pick them at create time.

SSH

Rowsafe never adds its own SSH key and doesn't need one: it works through its agent.

To log in yourself, add up to 10 SSH public keys when you create the server, and the addresses that may reach SSH. SSH stays closed while that list is empty. Log in as:

CloudUser
DigitalOceanroot
AWSadmin (Debian's default)
Azurerowsafe
OVHclouddebian (ubuntu where the region only has Ubuntu)

Rowsafe adds keys only at creation. To add one later, use your cloud's own tools.

Change the size

On the server's page, click Resize and pick a size. The disk can grow, never shrink.

The database is offline for a few minutes while the server restarts. Rowsafe saves a Mark first.

The server keeps its data and addresses. It needs the agent online and backups on. On AWS, the new size needs the same processor type (ARM or x86). On Rowsafe Cloud, see Change the size.

Delete the server

On the server's page, click Delete server and type its name.

  • Deleted in your cloud: the server, its disk, its firewall and its public address (where Rowsafe made them). Billing stops.
  • Kept: the backups in Rowsafe Storage. Restore them on another server with your passphrase. That's why you must save it first.

Backups are deleted only if you remove the database from Rowsafe, after 30 days, with an email a week before (details). If Rowsafe can't delete something (a revoked token, for example), the page says so.

What Rowsafe does with your cloud account

  • Acts only when someone clicks: create, resize, firewall changes and delete. Never on its own.
  • Tags everything it creates (rowsafe, or rowsafe=1 on AWS) and never touches anything else.
  • Keeps the credentials encrypted, never shows them again, and logs every change in the audit log.
  • Never sees your data: database passwords and the passphrase reach only your browser, encrypted.

To stop it, revoke the token in your cloud (each cloud's page says how), or remove the account under Settings → Cloud accounts once its servers are deleted. Your servers, backups, Proof and Pulse keep working; only resizing, firewall changes and deleting from the dashboard stop. See the trade-off.

Who can do this

Owners and admins create, resize and delete servers, connect cloud accounts and show the passphrase (in the dashboard or with a read-write API key). Members can see the servers. AI agents can't create, resize or delete servers in your cloud account, or see the passphrase; they can create Rowsafe Cloud servers as you.

Limits

  • Databases: the same versions and limits as Rowsafe Cloud. A standby and Clone to a new server are for PostgreSQL, MySQL and MariaDB. For MongoDB, Redis or SQLite, install Rowsafe on your own server (Quickstart).
  • Backups go to Rowsafe Storage at first, because your bucket's keys must never pass through Rowsafe. To move to your own bucket, you need SSH. A second copy in your bucket works too.
  • A standby needs your own bucket, not Rowsafe Storage, for now.
  • What Rowsafe may do and SSH keys are set at creation. Changing them later needs you to log in.
  • The connect steps for each cloud are new: tell us if anything doesn't match.
Edit on GitHub