Amazon Web Services
Regions across the UAE, Bahrain, India, the EU and beyond. The most common landing place for a self-hosted deployment.
Some businesses just want the system to work. Others answer to a regulator who cares exactly which country the database sits in. NearSync is built for both: run it in our cloud, or have us run it in yours - in your country, on your account, with your keys.
Two ways to run it
The fastest way in. We host, patch, back up and monitor; you pay per seat and never think about servers. Your organisation's data is isolated at the database layer - the same enforcement the security pageexplains - and you can export everything, any time, or move to self-hosted later without starting over.
The whole platform deployed into a cloud account you own, in the region your regulator expects, at a flat monthly price with no seat limits. We install it, keep it updated and watch it with you - but the account, the region and the keys are yours, and your production data never touches infrastructure we own.
Supported providers
Regions across the UAE, Bahrain, India, the EU and beyond. The most common landing place for a self-hosted deployment.
Includes Dammam - inside Saudi Arabia - for deployments that must not leave the Kingdom.
UAE and Saudi regions, and the full EU map. Often the answer where Azure is already the corporate standard.
Jeddah and Abu Dhabi regions for Oracle-first organisations.
Saudi sovereign cloud providers, for mandates that require a local operator as well as a local region.
On-premises deployments are scoped case by case on the enterprise tier. If it runs Linux and PostgreSQL, we can talk.
How self-hosted works
A cloud account you own, with the provider and region you choose. You hold root; we never do.
The full NearSync platform - database, APIs, files, AI workers - installed into that account by our team during onboarding.
Credentials live with you. Our production access is what you grant for updates and support, and you can see and revoke it.
Updates ship from the same pipeline that updates our cloud, and monitoring tells both of us if something is wrong.
UAE health and payment data must stay in the Emirates. Saudi government and critical-sector work must stay in the Kingdom, sometimes with a local operator. EU personal data wants GDPR guarantees wherever it sits. We will tell you honestly which deployment fits - and when the answer is "your cloud, your country", that is a thing we can set up this month, not a roadmap slide.