Run your projects on a dedicated server (Scale and Enterprise): pick a size on a slider, see the price first, and move with no downtime.
On the Scale and Enterprise plans your projects can run on a dedicated server that hosts only them, in our European data centers (Falkenstein and Nuremberg in Germany, Helsinki in Finland). Your project URL, API keys and connection strings never change, before, during or after the move.
#Sizes
Sizes go from Small (4 GB RAM) through Medium, Large, XL, 2XL, 4XL and 8XL (192 GB) to 16XL (384 GB or more); a size is offered only while a server of that size is available. The pricing page and Settings → Compute show the sizes available right now with live prices. Each size shows:
- Memory and CPU: whether the cores are shared vCPU or dedicated cores (each size uses the best-priced server with enough memory, so this can differ between sizes).
- NVMe disk for your databases (ECC memory is marked where the server has it).
- Connection limits for each project on the server: direct database connections and pooled client connections. They grow with the size and replace your plan's limits while the project runs on the server (never lower than the plan's).
- Billing: hourly for most sizes, monthly for the largest ones, and how soon it is ready (minutes, or a few hours for the largest sizes).
#Choose a server
- Open your project, then Settings → Compute.
- Press Choose a dedicated server, pick a location, then move the size slider: the price, memory, CPU, disk and connection limits update as you move it.
- Choose Only this project, or Every project of this account (new projects are created on the server too).
- Before you confirm you see the monthly price, the average hourly price (for hourly sizes), the amount for the rest of this month and whether your prepaid credit covers it.
The first dedicated server of an account, and every monthly-billed size, is approved by our team, usually within a business day. Then the server is created and your projects move onto it online, with a write pause of about a second.
#Large storage
For very large databases choose Large storage, enter the database size you need and see only servers with at least 1.5× that much usable disk: servers with large local NVMe drives, or a server with attached network storage of up to 10 TB (slower than local NVMe). Memory grows with the size you need.
#Billing
- Hourly sizes are charged hourly from your prepaid credit, starting when your projects run on the server. A full calendar month costs exactly the monthly price, so the hourly amount varies a little with the length of the month (the hourly price shown is the monthly price ÷ 730).
- Monthly sizes are charged per month in advance: the rest of the current month when your projects move onto them, then the full month on the 1st. Stopping one moves your projects back to shared servers right away; the month you paid is not refunded. A server that is still being set up can't be stopped.
- To start an hourly size you need 7 days of the server in credit, or automatic top-up with a saved card and at least 1 day in credit. A monthly size needs the rest of this month in credit, or automatic top-up. With invoice billing (Enterprise) neither applies. A month of the server must also fit under your monthly usage cap (not checked with invoice billing).
- If setup fails, nothing is charged.
- If your credit runs out you are e-mailed; after a grace period your projects move back to shared servers (no downtime) and the server is deleted, so you never build up debt.
#Resize or stop
Resize (hourly sizes) creates a server of the new size, moves your projects to it with no downtime and then deletes the old one; the confirm dialog shows the price difference. Stop using a dedicated server moves your projects back to shared servers and deletes the server; hourly billing stops at the hour that was started.
#Your own servers
Accounts that the StitchDB team has enabled (ask through support) can also run projects on servers they own, up to a maximum set per account (5 by default). Open Your servers in the dashboard sidebar and press Add server. Owners and administrators of the organization manage them.
- Requirements: a fresh Ubuntu or Debian server with at least 2 GB of memory and 20 GB of free disk, a public IPv4 address, root login with a password, and ports 22, 80, 443, 5432 and 6543 free and reachable.
- The root password is used once. The installer signs in with it, installs key access and then forgets it; it is never stored. The install steps and the install log are shown on the server's page, and Retry install takes the password again if needed.
- A server is either a database server (it runs projects) or a read replica of one of your database servers. Projects on a database server can use read replicas on your other servers.
Only your account can use them. StitchDB never places another customer's project, replica or failover copy on your server, and your server never receives keys or certificates of the platform or of other customers. It gets its own secrets, a certificate for the names of its own projects only (until that is issued, a few minutes after a project is created, a temporary certificate is served), a private network with your other servers only, and file storage on its own disk. Auth e-mail is relayed through StitchDB with your plan's hourly limit. Backups are taken by StitchDB and stored off the server.
Billing. Projects on your own servers do not count towards your plan's project limit, pay no extra-project fee and have no compute charge; read replicas on your own servers are free. Usage is billed as on any project: egress, monthly active users, Edge Function time, e-mail and AI. Plan limits such as database size still apply.
Moving projects. On a server's page, New project creates a project on it (you can also pick the server when creating a project), Move a project here moves one onto it and Move off moves one to another of your servers or back to StitchDB servers (where it counts towards the plan again). Between two of your own servers a move pauses writes for about a second and nothing else changes. Between StitchDB servers and your own, the database is copied while the project is read-only, and the database host name in your connection string changes; the project URL and API keys stay. Preview branches stay with their project.