Platform overview

tngatcloud is a multi-tenant platform-as-a-service that runs on Kubernetes. You describe what you want, and the platform provisions managed databases, object storage, sandboxes, edge functions and networking inside your own tenant namespace.

The hierarchy

Everything hangs off four nested scopes. There is no way to skip a level:

Layer	What it is	Why it matters
Organization	Your tenant. Owns members, roles, billing and audit.	Isolation boundary. Cross-org access is never implicit.
Project	A deployable unit inside an org.	Owns its own environments, variables, apps and services.
Environment	production / preview / development, plus custom ones.	Where variables and deployments live.
Service	A database, bucket, sandbox or edge function.	Always created inside a project.

No organization means no project. No project means no service. The console and the API both enforce this — a service can never float free of a project.

What you can provision

Managed databases — PostgreSQL, MySQL, MongoDB, Redis and pgvector, with

automated backups, replicas and connection pooling.

Object storage — S3-compatible buckets, private by default, with

pre-signed URLs and a CDN in front of public assets.

Sandboxes — long-running containers for development shells and small

services, each booting with a base toolchain.

Edge functions — JavaScript/TypeScript, Python, Go, PHP or Rust, served

from a global runtime.

Networking — private VPC isolation, API gateway middleware (rate limits,

circuit breaking, security headers), WAF and IP allow/block lists.

Where things run

The console is at cloud.tngat.com, the API at https://api.tngat.com, and every deployed app or bucket answers on a subdomain of app.tngat.com unless you attach a custom domain.