Skip to content
cirlume.
Menu

Data / 6 technologies

Pick the database for the questions you will ask.

Most products need one dependable database, and sometimes something fast beside it. PostgreSQL is our default for product data, whether we run it ourselves, on Neon or through Supabase. MongoDB or DynamoDB come in when the data or traffic suits them, Redis handles caching and queues, and we look after MySQL systems that already run a business.

Start a project

What we use

Data technologies we know well.

Why us

What we bring to data work.

  • One database per tenant

    In SoulCare, each care provider has its own PostgreSQL database, so one provider’s records never sit beside another’s.

  • Chosen for the data

    We pick relational, document or key-value stores for how the data is read and changed, not for what is fashionable.

  • Databases in your accounts

    Databases are created in your cloud accounts from the start, with backups and access you can see.

What you get

What a well-chosen stack gives you.

  • Data that stays correct

    Constraints, transactions and validation that stop bad records at the door.

  • Queries that stay fast

    Indexes and data models planned around how screens and reports read the data.

  • Changes you can repeat

    Versioned migrations applied the same way in every environment.

  • Backups you have tested

    Point-in-time recovery switched on, and restores rehearsed rather than assumed.

Where AI fits

AI in data work.

  • Vector search where your data lives

    PostgreSQL with pgvector (including on Supabase and Neon), MongoDB Atlas and Redis can all store embeddings next to your records, so search does not need a separate system.

    Knowledge assistants ↗

  • Access rules before retrieval

    Row-level security in PostgreSQL limits what an assistant can retrieve to what the signed-in user is allowed to see.

    Knowledge assistants ↗

Where it stops: Embeddings are derived from personal data too, so they need the same retention and deletion rules as the records they came from.

Choosing between them

Which one, and when.

PostgreSQL for related records and reporting, Neon when every branch needs its own database, or Supabase when you also want sign-in, storage and vector search for AI features on the same Postgres. MongoDB for nested or varied documents. DynamoDB for AWS products with known access patterns and spiky traffic. Redis beside any of them for caching and queues. MySQL when it is already in place.

What’s changing

Shifts to plan for.

Dates that affect data technologies, checked against the official sources.

  1. April 2026

    MySQL 8.0 reaches end of life

    Oracle moved MySQL 8.0 to Sustaining Support and recommends MySQL 8.4 LTS or 9.7 LTS.

  2. November 2025

    PostgreSQL 13 reaches end of life

    Version 13 had its final release on 13 November 2025. PostgreSQL 18, released that September, is the newest major version.

  3. May 2025

    Redis returns to open source

    Redis 8 added the AGPLv3 as a licence option, alongside its source-available licences.

Common questions

Data questions.

Can you migrate between databases?

Yes. We map the schema and queries, migrate with repeatable scripts and compare results against the source before switching over.

Who should own the database account?

You should. We set the database up in your cloud account, so access, billing and backups stay with your business.