Where your data lives
On Komuta servers, in the region you choose. The list of regions is public.
- Region
- Services, databases and volumes run on Komuta servers in the region you pick when you create them. The current list of regions is in the docs.
- Company
- Komuta is a trading name of SAGE TECHNOLOGY LTD, registered in England and Wales. More about the company on the about page.
- Data processing
- Our Data Processing Agreement follows Article 28 of the UK GDPR. The list of subprocessors is available on request under the DPA.
How workloads are isolated
- Runtime
- Every app on the managed platform runs in its own isolated, VM-based runtime, separated from other customers' workloads.
- Organizations
- Everything belongs to an organization: services, managed databases, members, Git connections and billing are scoped to it, and members only get the permissions an admin grants them.
- Network
- Services can talk to each other over a private network, and managed databases can be limited to it. An eligible service can also be isolated from the network and reconnected later.
Encryption and secrets
- In transit
- Every public address is served over HTTPS. Certificates for Komuta addresses and your own domains are issued and renewed automatically. Managed PostgreSQL, Valkey and RabbitMQ connections use TLS.
- Secrets
- Environment variables marked as secret are stored encrypted, are never shown again after you save them, and are left out of every export.
Your software supply chain
- Build scanning
- Every build is scanned for security issues and known vulnerabilities before it is deployed.
- Signed images
- For image deploys you can require that only images signed with your own key are accepted. The private key stays in your CI; Komuta never sees it. Unsigned images are rejected.
- No stored CI secrets
- GitHub Actions and GitLab CI can deploy with short-lived OIDC tokens, so no long-lived deploy key sits in your CI settings (CI deploy docs).
Access to your account
- Sign-in
- Email and password, Google or GitHub.
- Two-factor
- Any TOTP authenticator app. It's optional and each person turns it on for themselves; we strongly recommend it.
- Sessions
- See every device signed in to your account and close the ones you don't recognise.
- Team roles
- Organization admins invite members and set each person's role, resource permissions and module capabilities.
Protecting your apps
- Access protection
- On every plan: put a service behind a sign-in with SSO (Entra ID, Google Workspace, Okta, OIDC), one-time email codes, IP and country rules, rate limits and expiring share links (docs).
- Access logs
- Every sign-in, page view and refused request is recorded. Logs are kept 30 days by default; an organization can keep them for 30, 90 or 365 days, and export them as CSV.
- Security Center
- Brings findings, a risk score and network activity between your services into one place. Some host-level detection and blocking features aren’t available on the managed platform’s isolated runtime; the guide lists exactly what applies where.
Your data is yours
Leaving should be boring. Everything you run on Komuta can be taken elsewhere with standard tools.
- Apps
- Standard containers built from a Dockerfile in your own repository. They run anywhere containers run.
- Databases
- PostgreSQL can be dumped with
pg_dumpat any time. - Infrastructure
- A Stack exports as a
komuta.yamlfile. Secret values are left out on purpose. - After you leave
- If your account is closed you normally have 30 days to export your content (Terms).
Availability and incidents
- Live status
- Component status and 90 days of history at status.komuta.io.
- SLA
- Self-serve plans have no contractual uptime SLA today. What we do commit to is on the SLA & availability page.
- High availability
- On high-availability database plans, replicas run on separate physical nodes, so losing one server doesn't stop the service.
Backups and recovery
- PostgreSQLDaily full backup plus continuous WAL archiving. Retention 7 days by default, 2–365 adjustable. Manual backups any time.Restore the latest backup or any moment inside the window (point-in-time recovery).
- ValkeyDaily full backup of in-memory contents. Retention 7 days by default, 2–365 adjustable.Through a support ticket.
- RabbitMQDaily backup of configuration: exchanges, queues, bindings, users, policies. Messages in queues are not backed up.The broker can be rebuilt; queued messages can't be brought back.
- VolumesKept in multiple copies according to your plan. No separate backup action.Keep your own copy of files you can't afford to lose.
- Your codeLives in your Git repository.Roll back to any earlier revision from deployment history.
Deleting a database. Scheduled deletion keeps the instance and its backups for a 7-day grace period, and you can cancel it. Permanent deletion destroys the data and its backups immediately; even our support team can’t bring it back.
Compliance
Current certification and compliance status.
- UK GDPR / EU GDPRDPA availableArticle 28 DPA; data stays in the region you choose.
- SOC 2 Type IIComing soonWe will publish a target date here once an audit is scheduled.
- ISO 27001Coming soonWe will share the target date here once it is set.
Need a security questionnaire filled in or our DPA signed? Write to [email protected].