Start here
Fresh 4
2 shared vCPU · 4 GiB · 40 GiB
£8/ month max
£0.0119 / hour
- Fits
- Side projects, staging, small apps
- shared_buffers
- 1 GiB
- Connections
- 102
The £8 credit covers a full month
Managed Postgres
A dedicated PostgreSQL 18 server on your private network. TLS required, health checked every 15 seconds, restarted if it stops, and patched by us. A SQL editor and 41 extensions in the console. The price is the price of the machine it runs on.
From £8 a month max · £0.0119 / hour · the £8 new-account credit covers a Fresh 4 for a month
The decision
A Fresh 4 database costs exactly what a Fresh 4 machine costs. The difference is what you get and what you give up.
Want all of that? Create a machine and install Postgres yourself. Same price, same hardware.
Pricing
Three sizes, billed by the second, never more than the monthly price. Each is tuned for its memory, so the plan you pick is a database decision, not a VM one.
Start here
2 shared vCPU · 4 GiB · 40 GiB
£8/ month max
£0.0119 / hour
The £8 credit covers a full month
4 shared vCPU · 8 GiB · 80 GiB
£16/ month max
£0.0238 / hour
The £8 credit covers about two weeks
8 shared vCPU · 16 GiB · 160 GiB
£30/ month max
£0.0446 / hour
The £8 credit covers about a week
Prices in GBP, including VAT.
Not just a database
01
Query your database without leaving the console. Schema browser, autocomplete, 90 days of history, saved queries, EXPLAIN, and CSV and JSON export.
Safe on production. It opens read-only. Each run is one transaction that commits only if every statement succeeds.
02
41 we build and test against PostgreSQL 18, each with a plain explanation and an example. On or off from the Extensions tab.
03
Disk used of allocated, memory and CPU p95, and transfer, recorded every five minutes per database, with a plain note when something needs a look.
Where it sits
Anything you run on fresh.dev reaches the database over its private address, with no public exposure. Something elsewhere connects over the internet only if you turn public access on when you create the database and add its IP to the allowlist.
Specifics
The things you’d otherwise have to email us to find out, including the ones that are a no.
Extensions
Built and tested against PostgreSQL 18. Turn one on from the database’s Extensions tab; the console says first if a change needs a restart.
A 1,536-dimension column for OpenAI-style embeddings, an HNSW index, and a nearest-neighbour query.
alter table products add column embedding vector(1536);
-- cosine distance; build it after loading the embeddings
create index products_embedding_idx
on products using hnsw (embedding vector_cosine_ops);
-- the 10 products most similar to a query embedding
select id, name, 1 - (embedding <=> $1) as similarity
from products
order by embedding <=> $1
limit 10;
Keep the index in memory for fast queries. A vector takes 4 bytes per dimension, so 500,000 rows of 1,536 dimensions is about 3 GB before the index's own links: that wants a Fresh 8 or larger.
Delete expired sessions every night at 03:00 UTC, and see how recent runs went.
select cron.schedule('expire-sessions', '0 3 * * *',
$$delete from sessions where expires_at < now()$$);
select jobid, status, start_time, return_message
from cron.job_run_details
order by start_time desc
limit 10;
It needs a library loaded at start-up, so enabling it restarts PostgreSQL once (about ten seconds).
Shops with a location, a spatial index, and the ten nearest to a point.
alter table shops add column location geography(Point, 4326);
create index shops_location_idx on shops using gist (location);
select name, st_distance(location, st_makepoint(-0.1276, 51.5072)::geography) as metres
from shops
where st_dwithin(location, st_makepoint(-0.1276, 51.5072)::geography, 5000)
order by metres
limit 10;
Use geography for latitude and longitude on the Earth's surface (distances in metres); geometry for planar data and the full function set.
A hypertable of readings, hourly averages, and dropping data older than 90 days.
create table readings (time timestamptz not null, sensor int, value double precision);
select create_hypertable('readings', by_range('time'));
select time_bucket('1 hour', time) as hour, avg(value)
from readings
where time > now() - interval '1 day'
group by hour order by hour;
select drop_chunks('readings', older_than => interval '90 days');
It needs a library loaded at start-up, so enabling it restarts PostgreSQL once (about ten seconds).
Need one that isn’t here? Email help@fresh.dev with its name.
Questions people ask
Yes, if you chose public access when you created the database: add the other host’s IP address to its trusted sources. TLS is required either way. Anything you run on fresh.dev should use the private address instead; it never touches the internet.
pg_dump it, then pg_restore into the connection string the console shows you: over the private network from a fresh.dev machine, or from anywhere on your trusted sources. Add --no-owner, because you restore as the database’s owner rather than a superuser.
There’s no in-place resize yet. Create a bigger database, pg_dump the old one into it over the private network, then delete the old one. Both are billed by the second while you move.
It opens read-only. Writes have to be switched on, and each run is one transaction that commits only if every statement succeeds. Your query history is kept for 90 days.
We install security updates for the system underneath and PostgreSQL 18 minor releases automatically. Planned maintenance is announced on the status page at least 48 hours ahead. PostgreSQL 18 is the only major version for now.
Email help@fresh.dev with its name. We add the ones people ask for once we’ve built and tested them against PostgreSQL 18.
Query it in minutes
Name and size — a plan, a name, public access on or off.
Watch it come up — the console shows each step.
Copy the connection string, or just open the Query tab.