PostgreSQL
Open source, strict,
extensible
PostgreSQL is an object-relational database with a long history and a strict approach to data types. It is the usual choice when data models get more complex, when many writes happen at once, or when extensions are needed.
What PostgreSQL is built for
PostgreSQL has been developed since the 1990s by an open community under a permissive licence. It is object-relational, sticks closely to the SQL standard and is strict about data types — occasionally inconvenient while developing, and the reason less nonsense ends up in the table once it is running.
Technically, what stands out is concurrency: with multiversion concurrency control, reads and writes do not block one another. On top of that come capabilities that elsewhere require systems of their own — JSONB for semi-structured data, full-text search, window functions, materialised views.
It is extensible too: extensions such as PostGIS for geodata, or pgvector for embeddings from AI models, have ecosystems of their own. We run the common ones; with more obscure extensions we take a look first, because they can be tied to version jumps.
- Object-relational, close to the SQL standard
- MVCC: reading does not block writing
- JSONB for semi-structured data
- Window functions, materialised views
- Full-text search built in
- Extensions such as PostGIS
- Open source, no licence fees
PostgreSQL or MySQL?
The honest answer first: if the application dictates a system, the question is already answered. Standard software and content management systems usually bring their decision with them.
Where the choice is open, these are the points that normally decide it.
Rather PostgreSQL
- Complex data models and queries
- Many concurrent writes
- Strict demands on data consistency
- Geodata or other extensions
Rather MySQL or MariaDB
- Common web and content applications
- The application expects it
- Existing knowledge in the team
What we take on
Provisioned on its own VM
The instance runs on its own virtual machine with guaranteed resources, separate from the application server if you want it that way.
MoreMaintenance and security updates
We keep the operating system and the database software current. The annual change of version is agreed with you in advance.
Monitoring and fault resolution
24/7 monitoring. Which response times apply is set out in the contract.
MoreBackups while it runs
Backups are taken while the database is running, and they are consistent — it does not have to be stopped. Frequency and retention we agree together.
MoreFrequently asked questions about PostgreSQL
Does PostgreSQL cost licence fees?
No. PostgreSQL is under a permissive open-source licence; there are no licence fees for the database software itself. What you pay for are the resources of the VM and the support.
When is PostgreSQL the better choice than MySQL?
With more complex data models, many concurrent writes, strict demands on data consistency, and when you need extensions such as PostGIS. With common web and content applications the software often makes the choice for you.
Do you run PostgreSQL in a highly available setup?
Yes. Streaming replication, failover clusters — usually with Patroni — and point-in-time recovery from the write-ahead logs: we set them up and we run them. Which of them is needed depends on how long the application may be down and how much data loss would be bearable; we work that out before we build anything.
Do you support extensions such as PostGIS?
The common ones, yes — PostGIS for geodata and pgvector for embeddings from AI models are the two we are asked about most. What comes with the usual scope we run; with more obscure extensions we take a look first, because they can be tied to version jumps. Tell us which one the application needs and you will get a clear answer rather than a maybe.
Can I move my existing PostgreSQL database?
In principle yes. How the move runs and what it costs we clarify beforehand — it depends on the size, on the acceptable downtime, and on whether a version change happens at the same time.
Where do the databases run?
In our data centres in Hanover, Wolfsburg and Frankfurt, certified to ISO 27001 based on BSI IT-Grundschutz (BSI-IGZ-0552-2023). No CLOUD Act.
Sovereignty
Paving the way for digital sovereignty
-
Owner-managed since 1997
As an owner-managed operator with our own data centers, we make our decisions independently and are subject exclusively to German / EU law.
-
100% made in Germany
Our data center, product development, and customer support are all based in Germany for your digital sovereignty.
-
24/7 Customer Support
We are here for you: 24/7/365 customer support, in English and German
Is PostgreSQL right for your application?
Tell us about the data model — we will tell you what makes sense.
- We will get back to you as soon as we can.
- No obligation, free of charge.