A cluster of your own, on our own hardware.
Managed PostgreSQL. A dedicated always-on cluster in our data centre in Stockholm, sized by vCPU and memory with the disk included. One monthly price, patching handled, nothing metered on top.
- from USD 5 / month a month to start
- 16 – 18 Postgres versions
- Included disk on every size
- Included patching
# always up, no cold start$ psql postgresql://orders-prod…/orderspsql (18.6)$ SELECT count(*) FROM orders; count ------ 48211
- Size2 vCPU / 2 GB
- Disk4.1 / 25 GB used
- Nodes1
AVAILABILITY
Always on
No idle timeout and no cold start
ENGINE
PostgreSQL
Versions 16 through 18, newest by default
FROM
$5a month
1 vCPU, 512 MB, 5 GB disk
WHERE
Stockholm
Our own data centre, not resold
A size, then a connection string
Three steps to a database you can query
Nothing to provision by hand and nothing to tune before it works. Pick a version and a size, and the cluster is yours a minute later.
- 01
Choose the version and the size
PostgreSQL 16, 17 or 18, newest by default, on a size measured in vCPU and memory. The disk comes with the size, and the monthly price is shown before anything is created.
- 02
Copy the connection string once
When provisioning finishes you get the host, database, user, and a ready-made connection string. The password is shown once — put it in the secrets manager before you leave the page.
- 03
Query it from the panel or your app
The Data tab browses tables and runs SQL without a client installed. Your apps reach the same cluster over the project's own network.
What a database includes
Managed, and still sized by you
Cosmoner runs the servers and the patching. How much capacity the database has stays a decision you make per database.
Runs on our own hardware
Every cluster runs on capacity Cosmoner owns and operates, in our own data centre in Stockholm — not resold from a hyperscaler. The price is lower for it, and the people who answer support tickets are the people who run the servers.
Cosmoner infrastructure
No allowance to run out of
The capacity is reserved for your database alone. There is no compute allowance, no idle timeout, and no cap that suspends it mid-month — a busy day costs exactly what a quiet one does.
Fixed monthly price
PostgreSQL, versions you choose
PostgreSQL 16 through 18, newest by default, picked when the cluster is created, so a framework or extension that is not ready for the newest is not a blocker. The major version is then fixed for the life of the cluster.
PostgreSQL 16 – 18
Sized by CPU and memory
Pick the vCPU and memory the workload needs and the disk comes with it. Sizes start at 512 MB for development and staging, where a cluster of your own still beats sharing one.
Disk included
Read and edit without a client
The Data tab pages through tables, runs SQL, and edits rows straight from the panel. Read access is enough to browse; changing data needs write access on the project.
Built into the panel
Next to the apps that query it
The cluster sits on the same infrastructure as the apps in your project, so queries do not leave the building. Storage is persistent and survives restarts and maintenance.
One project, one network
Always-on
Capacity you are buying, not usage you are metering
A cluster is dedicated and sized by you. There is no sleeping, no allowance, and no usage cap: the monthly price is the same whether the database is busy or idle, which is exactly what you want under steady traffic.
- PostgreSQL 16, 17 or 18, on a size chosen for the workload: a 512 MB development database from $5, 1 GB and 2 GB above it.
- The disk is part of the size and included in the price. There is no storage line, no per-node multiplier, and nothing that grows the bill on its own.
- Runs on Cosmoner's own hardware in Stockholm, next to the apps that query it. Storage is persistent and survives restarts and maintenance.
- One node per cluster today. Standby replicas are on the roadmap and will be priced as a second node when they land, never switched on behind your back.
- EnginePostgreSQL 18
- Size2 vCPU / 2 GB
- Disk25 GB, included
- RegionStockholm (Cosmoner)
- Nodes1
# priced before anything is createdone monthly price, disk included
The sizes
Three sizes, and what separates them
Each size is one vCPU-and-memory pairing with its disk included. The create flow carries the current monthly price for each one.
1 vCPU / 512 MB
- Disk
- 5 GB
- Price
- $5/mo
1 vCPU / 1 GB
- Disk
- 10 GB
- Price
- $10/mo
2 vCPU / 2 GB
- Disk
- 25 GB
- Price
- $19/mo
The 512 MB size is capped at 50 connections, so put a pooler in front of it if your framework opens more.
Where it runs
Next to the app that queries it
Every cluster runs in Cosmoner's own data centre in Stockholm, on the same infrastructure as the apps in your project — so a query never crosses a supplier's network to reach its data.
- se-stoStockholm, Sweden
One project
What it plugs into
A database is billed on the project's subscription alongside the apps that query it, behind the same roles and the same API keys.
What it costs
A size — never a per-query line
One fixed monthly price for the capacity you reserved. Nothing is metered on top of it, so the invoice is the same number every month until you change size.
- The cluster
- from USD 5 / month
- One monthly price for the vCPU, memory, and disk you picked. The same price whether the database is busy or idle, and nothing sold on top of it.
- Storage
- Included
- The disk is part of the size. There is no storage line, no per-node multiplier, and nothing metered that can grow the bill on its own.
- Queries and bandwidth
- Not metered
- You bought the capacity, so using it costs nothing extra. There is no per-query line and no egress charge between the cluster and the apps in your project.
- Patching
- Included
- Minor-version patching is handled for you. The major version is fixed for the life of the cluster, so an upgrade never happens without you asking for it.
Every size shows its monthly price in the create flow, and a database created mid-month is prorated from the day it is created.
Questions worth answering up front
Sizing, size changes, versions, and connecting are covered in the Databases guide.
- What size should I start on?
- Start from the working set rather than the total data: Postgres is fastest when the rows you query often fit in memory. The 512 MB size is for development, staging and side projects, and is capped at 50 connections — put a pooler in front of it if your framework opens more. Move up when queries start hitting the disk rather than the cache.
- Can I change size later?
- Yes. The cluster's detail page lists every size next to your current one, tells you what changes before anything is charged, and applies the change prorated against your billing period. A smaller size is unavailable while the database holds more data than its disk includes.
- Can I upgrade to a newer major version?
- Not in place. The PostgreSQL major version is fixed for the life of a cluster, so moving to a newer one means creating a new database and migrating your data into it. Pick an older version only when something you depend on is not ready for the newest.
- Is there a standby replica?
- One node per cluster today. Standby replicas are on the roadmap and will be priced as a second node when they land, never switched on behind your back. Storage is persistent, so a restart or a maintenance window does not cost you the data.
- What if I lose the password?
- Rotate it from the cluster's detail page and update whatever was using the old one — rotating invalidates the previous password immediately. The password is shown once when provisioning finishes, so the safe habit is to store it as a secret before leaving that page.
A different job
Handing databases to your own clients
Shared databases are a separate product. They exist for giving your end-clients isolated, pooled databases on one shared PostgreSQL cluster, rather than for running your own application's data.
Each tenant gets its own database and its own credentials on a cluster you do not have to size, with a connection limit and a storage limit per tenant.