Appunvs Cloud overview

Appunvs Cloud is powered by the independent Mortar Backend-as-a-Service project. Applications can use its public APIs and SDKs for database, authentication, files, and other backend capabilities without becoming a Fabric or Keel project.

Features and platform management

The ten application features are Auth, Database, Storage, Realtime, Functions, Analytics, Cronjob, Queues, Messaging and Secrets. Go packages and HTTP namespaces use lowercase names. This inventory does not imply a matching management module in every SDK or that every feature is enabled in every deployment.

App User third-party connections and external-app authorizations belong to Auth. Custom Domains configure project API access and belong to platform management, alongside plans, top-ups, capacity and usage.

Project and identity boundary

• Each Mortar project is an independent tenant.
• Application end-user identity is separate from the developer account that creates and manages projects.
• End-user auth supports email/phone plus Mortar-managed Apple, Google, WeChat, and Alipay provider connections.
• Bundle-safe public credentials cannot gain account-management or service-role privileges.
• Applications built with Fabric or Keel may choose Mortar, but the three products remain independent.

Usage principles

1. Create and configure a project through the current Appunvs Cloud product interface.
2. Give clients only project configuration explicitly documented as public.
3. Keep administrator, service-role, and deployment credentials in controlled server environments.
4. Treat the current APIs, SDKs, and product UI as authoritative; unpublished designs are not delivered features.

This site publishes curated user documentation only. Internal architecture, operations runbooks, cost models, draft SLOs, historical decisions, and undelivered roadmap items are not public product commitments.