Couchbase · Cloud database
Cloud database in Saudi Arabia: managed Capella or Couchbase on Kubernetes
A cloud database runs on cloud infrastructure, either operated for you as a service or run by your own team. For a Saudi workload the choice turns on where the data may live and who will operate the cluster for years. This page sets out three ways to run Couchbase as a cloud database: Couchbase Capella as a managed service, including its Dammam region, and self-managed Couchbase Server on Kubernetes or in your own data centre. Interkey, a Couchbase technology partner, sells Capella and implements all three.
Orientation
At a glance
The whole page in one table, before the detail.
- Database as a service
- Couchbase Capella, operated by Couchbase on AWS, Google Cloud or Microsoft Azure
- Region in the Kingdom
- Capella lists Google Cloud me-central2 (Dammam), as of 2 November 2026
- Self-managed on Kubernetes
- Couchbase Server run by the Couchbase Autonomous Operator in a cluster you control
- Self-managed on your servers
- Couchbase Server in your own data centre in the Kingdom
- How it is billed
- Capella per node per hour; self-managed by subscription per production node
- What Interkey does
- Sells Capella, then sizes, models, migrates and operates any of the three from Riyadh
In short, for decision makers
- Three models: Capella as database as a service, Couchbase Server on Kubernetes, or Couchbase Server on your own servers.
- A region in the Kingdom: Couchbase lists Google Cloud's Dammam region for Capella, as of 2 November 2026.
- Residency decides first: a Saudi region keeps the cluster's data in Saudi Arabia; backups, replication and support access still need checking.
- Operation decides second: a managed NoSQL database removes most daily work; self-managed gives you control and the work.
What a cloud database means for a Couchbase workload
The phrase covers two things. In the first, a provider runs the database for you: you choose a size and a region, and the provider handles deployment, patching, backups and scaling. That is database as a service, or DBaaS. In the second, the database runs on cloud infrastructure but your own team, or a partner, operates it. The difference is who carries the work.
Couchbase offers both. Couchbase Capella is Couchbase's fully managed service. Couchbase Server is the same platform, run by you. Capella provides SQL++ queries, full-text search, eventing and vector search indexes, with App Services for mobile sync.
Cloud database options for a Saudi workload
| Question | Capella (managed) | Self-managed on Kubernetes | Self-managed on your servers |
|---|---|---|---|
| Who runs the cluster | Couchbase | Your team or Interkey, with the operator automating routine tasks | Your team or Interkey |
| Where the data sits | A Capella region you choose, including Dammam | The Kubernetes cluster and storage you choose | Your data centre in the Kingdom |
| How it is billed | Per node per hour, pay-as-you-go or prepaid credits | Subscription per production node, plus your infrastructure | Subscription per production node, plus your hardware |
| Getting started | A cluster typically deploys in under 5 minutes, as Couchbase states | A Kubernetes cluster must exist and be ready first | Servers, storage and network are built and sized first |
| Upgrades and patching | Handled by the service | Declared in the cluster specification and applied by the operator | Planned and run by whoever operates it |
| Fits best when | The data may sit in a Capella region and you want little to operate | You already run Kubernetes and want the database beside your applications | Your rules require infrastructure you operate yourself |
Decide in this order: where the data may live, who will operate the cluster for five years, what the workload needs in latency, consistency and scale, and only then the plan, sizing and price.
Database as a service: Couchbase Capella and its Dammam region
Couchbase publishes the regions Capella supports on each cloud. As of 2 November 2026, that list includes Google Cloud me-central2 in Dammam, Saudi Arabia, with App Services available there. Nearby regions are AWS me-central-1 in the UAE, AWS me-south-1 in Bahrain and Microsoft Azure UAE North. Regions are added over time, so check Couchbase's current list before you decide; the Capella page keeps the full table.
Read more
Capella is billed per node per hour, scaled by each node's vCPU and RAM, either pay-as-you-go or from prepaid credits. Disk storage is part of the hourly rate; backups and data transfer are billed separately. The plans are Basic, Developer Pro and Enterprise. Each organisation can run one free Capella cluster, but Couchbase's list does not mark Dammam for the free tier.
Self-managed Couchbase on Kubernetes
Teams that run their applications on Kubernetes can run the database there too. Couchbase's documentation describes the Couchbase Autonomous Operator as a Kubernetes extension for running Couchbase Server: you declare the cluster you want, and the operator makes the running cluster match it. The same documentation lists support for upstream Kubernetes, Red Hat OpenShift, Amazon EKS, Google GKE and Microsoft AKS, and states that the operator deploys Couchbase Server Enterprise Edition.
Read more
According to Couchbase, the operator handles provisioning, scaling, upgrades and auto-recovery, along with persistent volumes, server groups, cross data centre replication (XDCR), TLS certificate rotation, and backup and restore. That takes routine work off your team, but someone must still understand both Kubernetes and Couchbase: storage classes, node sizing, failure domains and upgrade rehearsals remain decisions. Our Kubernetes platform page covers the platform underneath.
The Kubernetes cluster can sit in a cloud account you control or in your own data centre in the Kingdom, so one operating method serves both residency answers.
Data residency for a cloud database in Saudi Arabia
A Capella cluster in Dammam keeps the cluster's data in a Saudi region. Before you treat that as the whole answer, settle these points with your compliance owner:
- Backups. Where they are stored, and for how long.
- Replication. Whether any cross-region replication (XDCR) is configured, and to where.
- Connected services. Where App Services, monitoring and logs are processed.
- Support access. Who outside your organisation can reach the data.
- Classification. Some data classes may require infrastructure you operate yourself.
Read more
The rules behind these questions come from Saudi authorities, not from a database vendor. The National Cybersecurity Authority (NCA) publishes cybersecurity controls, including controls for cloud computing, and the Saudi Data and AI Authority (SDAIA) oversees the Personal Data Protection Law. Which applies depends on your sector and your data. Monitoring data raises the same questions; our guide to telemetry data residency works through them.
RelatedNational Cybersecurity Authority (NCA)Saudi Data and AI Authority (SDAIA)guide to telemetry data residency
When each cloud database model fits
A managed NoSQL database such as Capella usually fits when the data may sit in a Capella region, you would rather not run a distributed database yourselves, or you want to start small and scale per node.
Couchbase on Kubernetes usually fits when your platform team already runs Kubernetes with confidence and wants the database declared like the rest of the platform.
Read more
Couchbase Server on your own servers usually fits when your rules require infrastructure you operate yourself, or the workload must sit next to systems that cannot reach a public cloud region.
If a relational system is serving its load and growth is modest, moving it buys risk with no return. The Couchbase implementation page sets out when Couchbase is the wrong tool.
How Interkey delivers a cloud database
-
Workload review.
Access patterns, consistency needs, data volume, growth, and the residency rules that apply.
-
Model choice.
Capella, Kubernetes or your own servers, and the region, plan or cluster for it.
-
Sizing and quote.
Node sizes, availability zones, backup policy, and the Capella credits or the subscription to buy.
-
Data modelling and migration.
Documents designed for how the data is read, then a dual-run migration with a rehearsed cutover and rollback.
-
Operation.
Monitoring, scaling, backup checks and support after go-live, under a written scope.
Cost, timeline and support for a cloud database in Saudi Arabia
Interkey sells Couchbase Capella, so one quote can cover the Capella credits, the plan and our implementation work. For self-managed Couchbase Server, on Kubernetes or on your own servers, the subscription is quoted alongside our work. Couchbase's published rate card uses a US region as reference, so a Dammam price is confirmed for your organisation.
Read more
How long a move takes depends on how many services use the data, how far the current model is from documents, and how long the dual-run must last; we estimate it as a range once those are known. Our cloud database migration page covers the move itself. Support comes from our engineers in Riyadh, in Arabic or English, and managed services can operate the cluster after go-live under a written scope.
Couchbase is an Interkey technology partner. The platform belongs to Couchbase. Interkey's engineers in Riyadh do the assessment, migration, tuning and operation.
Questions buyers ask
Can a cloud database keep our data inside Saudi Arabia?
Yes, in two ways. Couchbase lists Google Cloud's Dammam region for Capella, as of 2 November 2026, and self-managed Couchbase Server can run in your own data centre in the Kingdom. Either way, check where backups and replication run.
What is the difference between database as a service and running Couchbase on Kubernetes ourselves?
With Capella, Couchbase runs the cluster. On Kubernetes, the Autonomous Operator automates provisioning, scaling and upgrades, but your team or Interkey owns the cluster and its storage.
How is a managed NoSQL database priced for a project in KSA?
Capella is billed per node per hour, from pay-as-you-go or prepaid credits, with backups and data transfer on top. We confirm the Dammam price for your organisation and quote our work alongside.
How long does it take to move an existing database to a cloud database?
It depends on how many services use the data, how far the current model is from documents and how long the dual-run must last. We give a range after a workload review.
Can Couchbase run on our own Kubernetes cluster in an in-Kingdom data centre?
Couchbase's documentation lists upstream Kubernetes and Red Hat OpenShift among the platforms the Autonomous Operator supports, so a cluster in your own data centre is an option. We confirm versions and storage during the review.
Who supports our cloud database after go-live, and in which language?
For Capella, Couchbase operates the service and the plan sets its support response. Interkey's engineers in Riyadh support your team in Arabic or English, and can operate a self-managed cluster under a written scope.
Next
Related pages
Next step
Choose a cloud database model for your workload
Tell us what the database serves, roughly how much data it holds, whether you run Kubernetes, and where the data must stay. We will reply with the model we would choose.
Or directly
+966-11-2180999 [email protected]Tawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia