The default engine, run your way.

Managed PostgreSQL two ways — on dedicated DB VMs you control, or as DBaaS on an HA setup we own and operate. Full admin credentials to your database either way.

Dedicated DB VMsDBaaS on HA clusterspgvector ready

Talk to us All Databases

Capabilities

Postgres you don’t have to babysit

Production-grade PostgreSQL with built-in resilience, automation and control so you can ship faster and sleep better.

HA that isn't yours to build

DBaaS runs on a multi-node cluster with synchronous standbys and automatic promotion, rehearsed on a schedule rather than discovered during an incident.

Failover in seconds, unattended →

Full admin credentials

Superuser-grade rights to your database on both models — roles, schemas, extensions and grants are yours to set, with no ticket in between.

Your database, your control →

Point-in-time restore

Continuous WAL archiving lets you rewind to the minute, and every backup is proven by a real restore drill instead of a green tick.

Recovery tested, not assumed →

Extensions maintained

PostGIS, pgvector, pg_stat_statements, TimescaleDB and the rest of the common set — installed, version-matched and upgraded with the engine.

Geospatial and AI, natively →

Connection pooling

PgBouncer in front of the cluster absorbs thousands of short-lived application connections without exhausting backend slots.

Bursty apps stop toppling the DB →

Private by default

Instances sit on your virtual networks with TLS in transit and encryption at rest — no public endpoint unless you ask for one.

Nothing exposed by accident →

Upgrades planned with you

Minor patches applied in your maintenance window; major versions rehearsed on a clone before anything touches production.

No forced vendor schedule →

Logical replication & migration

Replication slots, dump/restore and CDC feeds move you in from an existing estate and out to analytics without downtime windows.

Arrive and leave on your terms →

Query-level observability

Slow query capture, index and bloat reporting, lock and replication lag metrics, streamed into your dashboards and alerts.

See the query before users do →

Scale without a rebuild

Add CPU, memory, storage or read replicas in place — the endpoint stays the same, the application never learns anything changed.

Growth is a setting, not a project →

Resilient by designBuilt to continue, even when hardware fails.

Predictable performanceConsistent I/O for the apps that matter.

Efficient at scaleOne flat fee. Scale without waste.

Backed by humansReal experts. Real support. Every time.

Choose your deployment

Dedicated DB VMs, or DBaaS

The same operated PostgreSQL in both — the difference is whether you own the machines, or just the database on an HA setup we run.

ProductionEdgeComing soon

MODEL 01

Dedicated DB VMs

The whole stack is yours

PostgreSQL on dedicated virtual machines in your VPC — root on the OS, full control of the engine, any extension or configuration you need. We provision, patch and watch the infrastructure underneath.

Best for

Custom extensions & tuningRegulated workloadsLift-and-shift estates

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

DB VMSingle dedicated VM · PITR 7 daysSign in →DB VM HAVM pair across zones · automatic failoverSign in →CustomAny shape, topology and retention windowSign in →

MODEL 02Production default

DBaaS

Rights to the database, not the machines

Your databases on a multi-node HA setup owned and managed by YallaCloud. You hold full admin credentials to the DB, with service and billing controls in the console — and never touch a VM.

Best for

Production applicationsSaaS backendsTeams without DBAs

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

StandardHA cluster · PITR 14 daysSign in →PlusHA + read replicas · PITR 30 daysSign in →CustomAny replica count, retention and pooling setupSign in →

Build it yourself

Size the database, then price it

Two calculators, one flow. Dedicated DB VMs size machines you own; DBaaS sizes databases on a cluster we own. Pick a model, shape the build, then sign in for the fee.

Which deployment model?This decides which calculator you get next.

Where does it run?Residency, backups and replicas follow the placement.

PostgreSQL version

Minor patches land in your window; major upgrades are rehearsed on a clone first.

Workload profile

Balanced CPU and memory for OLTP — the default shape.

Dubai · PostgreSQL 16 · Transactional

Who owns what

Your machines, or just your database

Both arrive fully operated, with backup, monitoring and failover. The difference is where your responsibility starts.

Dedicated DB VMsYou run the stackDedicated VMs in your tenancy — root on the OS, your engine configuration, your extensions. We keep the infrastructure healthy underneath.

Root access to OS and engine

Any extension, any configuration

Infrastructure patched and watched by us

Best for:DBA-owned estates and strict isolation

Explore Dedicated DB VMs plans

DBaaSWe own the clusterRights to the database only, on an HA setup we own and manage. Full DB admin credentials are yours, with dedicated controls for service and billing.

Full DB admin credentials, yours

Service controls: create, scale, restore

Per-database billing visibility

Best when:You want databases, not servers

Explore DBaaS plans

Who decides, who runs it

What each group gets from PostgreSQL

Four groups shape a cloud decision. Pick the one you belong to — the platform reads differently from each seat.

“The default engine, properly run”

An open-source database with enterprise operations behind it, in-country, with no licence exposure to manage.

GovernedSovereignPredictable

FAQs

What exactly do we get on DBaaS?

Rights to the database itself: full admin credentials, plus console controls for service operations and billing. The multi-node HA setup underneath is owned and managed by YallaCloud.

Do we get admin credentials?

Yes — full DB admin credentials on both models. On Dedicated DB VMs you additionally hold root on the operating system.

How is failover handled?

DBaaS runs on a multi-node HA setup that promotes automatically, typically within seconds. Dedicated DB VM pairs fail over the same way.

Are extensions available?

Yes — the common set including PostGIS and pgvector on DBaaS, and anything you like on your own dedicated VMs.

How far back can we restore?

Point-in-time restore from 7 to 30 days depending on the plan, with longer retention available on request.

Can we reach it privately?

Yes. Both models live on your virtual networks with no public endpoint unless you ask for one.

How is the flat fee different from public cloud pricing?

Everything inside the plan you opt for is included — no additional charge for the components that make it up. Public clouds meter each component on consumption, so the bill moves with usage. Here the plan is reserved for you and the figure you agreed is the figure you pay.

Can we drive it from Terraform and CI?

Yes. Every operation is exposed through the REST API, CLI and a maintained Terraform provider, with scoped API keys per team. If the console can do it, your pipeline can do it.

How do limits and quotas work?

Quotas are yours to shape — carve capacity per team or project and delegate inside it. Hard ceilings are a conversation, not a wall; the estate re-baselines at thresholds you approve.

Can security services be included in my plan?

Yes. Endpoint security, firewalls and WAF are scoped into the same flat fee when you add them — one figure, no separate security invoice.

Better together