What it does
Organisations own projects. Every record, user and definition of a project is stored under a project-specific prefix, each project has its own keys and signing secret, and a project moves through a lifecycle that can pause, suspend, export and purge it. Isolation is logical: tenants share one engine, one log and one process.
How it works
An organisation has members with owner, admin or member roles, and any number of projects. Creating a project mints its anon key, service key and signing secret. Everything a project stores uses a t_<project>___ prefix on both its kinds and its ids, so a request resolved to project A builds its reads, filters, searches and exports from A's prefix instead of filtering afterwards. Project ids are generated ULIDs.
Credentials sit on one of two planes. Project credentials (anon key, service key and end-user token) are bound to a single project and cannot manage organisations. Platform credentials (platform account tokens and the global key) manage organisations, projects and keys, and a platform administrator can act inside a project by sending X-Project-Id. The plane is decided once, when the credential is resolved.
A project has a lifecycle: provisioning, active, paused, suspended, deprovisioning and purged. Active and paused projects authenticate. Paused allows reads, refuses writes and keeps sessions renewable. Suspended, deprovisioning and purged projects refuse their keys. Transitions follow a fixed table, and each one is recorded as a tenant-operation record.
GET /admin/v1/projects/:id/export returns one project's namespace as integrity-hashed NDJSON: a header with a manifest, the entities with authentication material removed, and a trailer with a SHA-256 over the file. The manifest lists every class of internal state that was left out, and the x-kynetra-export-complete response header says whether the export is complete. POST /admin/v1/projects/:id/purge, for a platform super admin or the global key and for a project in the deprovisioning state, tombstones every entity under the prefix, deletes the project row and its keys, forces a checkpoint and reports the erasure scope: live checkpoint plus retained write-ahead log.
Where you reach it
- HTTP
POST|GET /admin/v1/orgs, GET|DELETE /admin/v1/orgs/:id - HTTP
POST|GET /admin/v1/orgs/:id/members, DELETE /admin/v1/orgs/:id/members/:uid - HTTP
POST|GET /admin/v1/orgs/:id/projects, GET|DELETE /admin/v1/projects/:id - HTTP
POST /admin/v1/projects/:id/status, GET /admin/v1/projects/:id/export, POST /admin/v1/projects/:id/purge - HTTP
POST /admin/v1/provision - Config
KYNETRA_RATE_LIMIT_PROJECT
Example
# Signed in as a platform account
curl -s -X POST "$KYNETRA_URL/admin/v1/orgs" \
-H "Authorization: Bearer $ACCESS_TOKEN" -H "Content-Type: application/json" \
-d '{"name":"Acme"}'
curl -s -X POST "$KYNETRA_URL/admin/v1/orgs/$ORG_ID/projects" \
-H "Authorization: Bearer $ACCESS_TOKEN" -H "Content-Type: application/json" \
-d '{"name":"storefront"}'
# returns the project, its anon_key and its service_key (shown once)
curl -s -X POST "$KYNETRA_URL/admin/v1/projects/$PROJECT_ID/status" \
-H "Authorization: Bearer $ACCESS_TOKEN" -H "Content-Type: application/json" \
-d '{"status":"paused"}'Limits
- Isolation is logical. Tenants share one engine, one log and one process. There is no per-tenant process, storage volume or encryption key.
- Platform accounts and the global key are operator credentials with deployment-wide authority. Issue them only to operators, and keep operator endpoints off the public internet.
- A purge is a tombstone plus checkpoint compaction, not cryptographic erasure. Earlier versions of the data remain in the retained log, in backups and restore-undo copies, in replica logs and in disk-store segments until compaction rewrites them. The purge response states this scope.
- Per-project entity and request limits exist in the data model, but no API in this release sets them. The default per-project request budget described under request protection applies.
- Some classes of internal state, for example usage metering and classification state, are not part of an export, so an export can be marked incomplete. Read the manifest before treating an export as a backup.
- The global API key addresses every namespace.
- Project key rotation and organisation membership changes are not written to the tamper-evident audit log. Lifecycle transitions are recorded as tenant-operation records.
Evidence
- On this siteMulti-tenancy
- Tests59 tenancy tests in the server (namespace scoping, separate user pools, lifecycle transitions, purge completeness and resumability, quota arithmetic, platform-plane credential checks) and, in the exporter, 22 export tests (integrity hash, redaction of authentication material, snapshot isolation, completeness manifest) and 11 lineage-export tests
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
Request a preview to talk through the limits above against your own workload.