2026-06-02DataMesh Consulting
2 June — platform migrated to Fly.io + Supabase: faster, leaner, single-region London
We moved the entire platform — public site, API, admin dashboard, scraping agent, queue and object storage — off our previous cloud onto Fly.io (London) with a Supabase Postgres database (also London). Same features, lower latency, ~50% lower run cost, and a simpler stack we can reason about end to end.
What changed
Today we completed a full infrastructure migration. Every moving part of
datameshconsulting.co.uk now runs on
Fly.io in London, backed by a Supabase PostgreSQL database (with the
pgvector extension for AI matching) in the same region.
Nothing about the product changed — the public tender pages, the API the iOS app talks to, and the admin monitoring dashboard all behave exactly as before. This was purely a foundation move.
Why
- Lower latency, single region. App and database now sit in the same
- Simpler stack. One platform for the web app, API, dashboard, the
- ~50% lower running cost at our current footing, with no feature loss.
- IPv4-clean, managed TLS. Hostnames resolve cleanly and certificates
How it went
We migrated the full corpus — ~56,000 tenders and ~46,000 AI embeddings — into the new database, verified vector search and authentication end to end, cut the public domain over with a short, reversible DNS change, and only then decommissioned the old environment. The web stayed up throughout; the API was validated before any traffic moved to it.
The migration tooling (deploy configs, a one-shot database-migration script and a staged teardown runbook) is checked into the repo, so the whole stack is now reproducible from source.
What's next
With the foundation simpler and cheaper, the focus returns to coverage — more Step-0 extractors and richer per-notice detail — and resuming the continuous scraping cadence.