Auth
End-user signup, login, OTP, and sessions, with project API keys kept separate from account credentials.
GO-NATIVE · APACHE 2.0
Appunvs Cloud is powered by the open-source Mortar project. Auth, data, files, realtime, and usage share one explicit project-tenant boundary. Any app can use it; Fabric and Keel are not prerequisites.
Mortar is Apache-2.0 open source · self-hostable · Appunvs Cloud is open for registration
APPLICATION CAPABILITIES
The public app client and account/admin client use different credentials. A key safe to ship in a client bundle never gains service-role or cross-project access.
End-user signup, login, OTP, and sessions, with project API keys kept separate from account credentials.
Postgres table and row CRUD stays inside the project tenant boundary, reinforced by server-side RLS.
One upload, download, and signed-URL API over local disk, Aliyun OSS, or Tencent COS.
SSE row changes, broadcast, and presence without forcing a heavier client connection model.
Invoke configured function endpoints, with cron and queue exposed as separate extensions.
Projects, balances, usage ledgers, and tier management live in an independent control plane.
TYPESCRIPT QUICK START
The TypeScript SDK is the reference implementation with the broadest coverage. The project UUID belongs in the host; there is no separate tenant option.
See the product overview and current capability boundaries →
npm install @mortar-ai/client
import { createClient } from '@mortar-ai/client';
const mortar = createClient({
url: 'https://<tenant>.api.mortar.appunvs.com',
apiKey: 'mtr_live_...',
});
const todos = await mortar.from('todos').select({ limit: 10 });
await mortar.from('todos').insert({ title: 'buy milk' });