Short answer: platforms that let you keep observability data in Singapore include TrueWatch, Grafana Cloud, Elastic, Splunk and LogicMonitor, with Dynatrace offering Singapore on request. For Indonesia, TrueWatch and Grafana Cloud run regions in Jakarta. Datadog, New Relic and Honeycomb do not list a Southeast Asia region as of October 2026.
If you run applications for customers in Singapore, Indonesia or the wider region, where your telemetry lives is now part of the buying decision. This guide covers which platforms host data locally, what personal data hides inside observability data, and the questions to ask before you sign.
Why data location matters for observability
Observability data is not just CPU graphs. Logs, traces and session replays often carry user IDs, IP addresses, emails and full request payloads. Where that data is stored matters for three reasons:
- Regulation. Singapore's Personal Data Protection Act (PDPA) and Indonesia's Personal Data Protection Law (UU PDP, Law No. 27 of 2022) govern how personal data is handled, including transfers abroad. Financial regulators such as MAS in Singapore and OJK in Indonesia may set additional requirements for the institutions they supervise.
- Customer contracts. Enterprise, banking and government customers increasingly ask where their data is processed, and some write it into procurement checklists.
- Latency and cost. Shipping telemetry from Jakarta or Singapore to Tokyo, Sydney or the US adds network delay and data transfer cost on every byte you send.
Data residency, data sovereignty and data localization
These three terms get used interchangeably, but they mean different things when you talk to a vendor or your compliance team.
| Term | What it means | What to ask a vendor |
|---|---|---|
| Data residency | The physical location where data is stored, usually chosen by the customer | Which region stores each data type I send? |
| Data sovereignty | Data is subject to the laws of the country where it is stored | Which legal entity operates the region, and which laws apply? |
| Data localization | A legal or contractual rule that data must stay in a specific country | Can you guarantee no copy, backup or processing leaves the country? |
Most teams in Southeast Asia need data residency. Some regulated workloads need localization, which is a stricter promise and should always be written into the contract.
What personal data hides in telemetry
Teams often assume metrics are safe and logs are the only risk. In practice, personal data shows up across every signal:
- Logs: email addresses, phone numbers and national ID numbers printed in error messages or debug output
- Traces: URL paths and query strings such as /users/12345 or ?email=, plus HTTP headers and database statements
- Real user monitoring and session replay: IP addresses, device IDs, form inputs and screen recordings
- Profiles and events: hostnames, usernames and custom attributes added by developers
This is why location is only half the answer. The other half is reducing what you send in the first place, with masking at the agent or pipeline, short retention for raw logs and role-based access to sensitive views.
Singapore and Indonesia rules at a glance
This section is general information, not legal advice. Check your specific obligations with your legal or compliance team.
- Singapore (PDPA): personal data can be transferred overseas, but the organisation must ensure the recipient protects it to a standard comparable to the PDPA. Keeping data in Singapore removes one layer of that assessment.
- Singapore financial services: MAS-regulated institutions also follow MAS guidelines on technology risk and outsourcing, which affect how cloud and SaaS providers are assessed.
- Indonesia (UU PDP): the law's transition period ended in October 2024. Cross-border transfers are allowed under conditions, such as the destination country offering equal or higher protection, adequate safeguards, or the data subject's consent.
- Indonesia sector rules: public-sector systems and OJK-regulated financial institutions can face stricter expectations about keeping data in the country.
For regulated sectors in Indonesia, a Jakarta region is often the simplest way to keep observability out of the compliance discussion.
Regions at a glance
| Platform | Singapore | Indonesia (Jakarta) | Other Asia-Pacific | Private or in-your-cloud option |
|---|---|---|---|---|
| TrueWatch | Yes | Yes | Singapore site serves Japan, Thailand, Malaysia, Vietnam and more | Private deployment, talk to us |
| Grafana Cloud | Yes (AWS; GCP via Google Cloud Marketplace) | Yes (AWS ap-southeast-3) | Sydney, Mumbai, Tokyo | Not listed |
| Elastic Observability | Yes | No | Tokyo, Sydney, Mumbai and others | Self-managed Elastic Stack |
| Splunk Observability Cloud | Yes (sg0) | No | Australia, Japan | Not listed |
| Dynatrace | On request | No | Sydney (standard); Tokyo, Mumbai on request | Dynatrace Managed |
| LogicMonitor | Yes (AWS) | Not listed | Not listed | Not listed |
| New Relic | No | No | Japan (through New Relic's Japan entity) | Not listed |
| Datadog | No | No | Japan (AP1), Australia (AP2) | Logs only, with BYOC Logs |
| Honeycomb | No | No | None (US and EU only) | Not listed |
| groundcover | Your own cloud | Your own cloud | Your own cloud | Runs inside your cloud account |
Regions checked against each vendor's public documentation in October 2026. Vendors add regions often, so confirm before you sign.
What to check before you sign
- Where each data type is stored. Some vendors keep metrics in one region but process logs, RUM or AI features elsewhere. Ask for every data type you send: metrics, logs, traces, sessions and profiles.
- Where backups and disaster recovery live. A primary region in Singapore does not guarantee the backup copy stays there.
- Where support and AI features process data. An AI assistant may send prompts and query results to a model hosted in another region.
- Who can access the data. Ask which staff, in which countries, can access your workspace, and how that access is approved and logged.
- Certifications. SOC 2 Type II and ISO/IEC 27001 are common baselines. ISO/IEC 27017 and 27018 cover cloud security and personal data protection in the cloud.
- Exit and deletion. Ask how long data is kept after you leave and how deletion is confirmed.
- Get it in writing. "Available on request" regions should be named in the contract, along with the data types they cover.
How to choose
| If you need... | Shortlist |
|---|---|
| Data stored in Indonesia | TrueWatch, Grafana Cloud |
| Data stored in Singapore with a broad managed platform | TrueWatch, Grafana Cloud, Elastic, Splunk, LogicMonitor; Dynatrace on request |
| Data that never leaves your own cloud account | groundcover, or a private or self-managed deployment |
| A large existing ecosystem and no in-country requirement | Datadog, New Relic |
If you are also weighing cost and feature fit, see our guide to [Datadog alternatives](INSERT LINK) and our [TrueWatch vs Datadog](INSERT LINK) comparison.
About TrueWatch
TrueWatch is an observability platform built for the AI era, headquartered in Singapore. It runs regional SaaS sites in Singapore and Jakarta, plus Frankfurt, Oregon and Johannesburg, so teams can pick a site based on infrastructure, latency and data location. The Singapore site serves customers across Asia-Pacific, including Japan, Thailand, Malaysia and Vietnam.
TrueWatch brings metrics, logs, traces, real user monitoring and AI telemetry into one platform, with Toby AI Agents to help with root cause analysis. It is SOC 2 Type II certified and holds ISO/IEC 27001, 27017 and 27018 certifications. TrueWatch is available on Google Cloud Marketplace.
FAQ
Does Datadog have a data center in Singapore? No. As of October 2026, Datadog's Asia-Pacific sites are AP1 in Japan and AP2 in Australia.
Does Datadog have a data center in Indonesia? No. Datadog does not list an Indonesia site. Teams in Indonesia sending data to Datadog use a site outside the country.
Which observability platforms have a data center in Indonesia? TrueWatch and Grafana Cloud both run regions in Jakarta.
What is the difference between data residency and data sovereignty? Data residency is where data is stored. Data sovereignty is which country's laws apply to it. A vendor can store data in Singapore while still being subject to laws elsewhere, so ask about both.
Do Singapore or Indonesian laws require observability data to stay in the country? It depends on your sector and the data involved. General data protection laws focus on how personal data is protected and transferred, while some sector regulators add stricter rules. Check with your legal or compliance team.
Can I keep observability data inside my own cloud account? Yes. groundcover runs inside your cloud account, Elastic and Dynatrace offer self-managed deployments, and TrueWatch offers private deployment options.
Keep your telemetry close to your users
TrueWatch runs regional sites in Singapore and Jakarta, so you can keep metrics, logs and traces in the region your customers and regulators expect. [Start a free trial](INSERT LINK) or [book a demo](INSERT LINK) to see which site fits your stack.
