Auth
User signup, login, phone OTP, email verification, password reset, and sessions.
CAPABILITIES
Clear app capabilities. Clearer trust boundaries.
Appunvs Cloud uses Mortar to separate the end-user application data plane from the account-management control plane. The list below stays within boundaries supported by current code and docs.
Public App Client
Project tenant
Account Client
CORE
Core application capabilities.
Clients use familiar auth, db, storage, realtime, compute, and usage shapes through the SDK.
Data
Tenant-isolated Postgres table and row CRUD, full-text search, and short-lived query caching.
Files
Upload, download, signed URLs, and metadata over local, OSS, or COS storage backends.
Realtime
SSE row changes, broadcast, and presence, with cache-backed cross-replica fan-out.
Compute
Invoke configured HTTP function endpoints; the current CLI does not deploy function code.
Usage
Per-project balances, usage ledgers, quotas, and compute-spec caps.
EXTENSIONS + CONTROL
Extensions stay out of the core ABI.
Each extension has its own service and delivery status. Administrative credentials remain server-side or in controlled operations environments.
Cron & queue
Scheduled function calls and a Postgres-backed job queue live in separate extension modules.
Custom domains
The control plane supports hostname claims and DNS verification; self-service TLS is not presented as delivered yet.
Account control
Accounts, projects, API keys, balances, and tier operations stay separate from the app data plane.
Four SDK foundations
TypeScript is the reference implementation. Swift, Kotlin, and Dart align on core semantics; check each SDK for extension coverage.