> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mibyanai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mibyan Apps

> Build, publish, and run web apps with a database, sign-in, storage, functions, payments, and a custom domain

**Mibyan Apps** takes a project from a request in chat to a live web app. The agent builds the project, and **Mibyan Cloud** gives it the services a real app needs: a database, sign-in for the app's own users, file storage, backend functions, email, SMS, payments, and a custom domain.

## From request to live app

```mermaid theme={null}
flowchart LR
  A["Describe the app in chat"] --> B["Agent builds the project"]
  B --> C["Preview"]
  C --> D{"Happy with it?"}
  D -- "Ask for changes" --> B
  D -- "Yes" --> E["Publish to production"]
  E --> F["Live app"]
  F --> G["Versions: every deploy is kept"]
  G -- "Roll back" --> F
```

You can start from a template or from a blank request, and ask the agent to configure services (for example, "add sign-in and a bookings table") as part of the conversation. The **App center** then shows what is live and lets you manage each service yourself.

## The App center

Open your app from **Apps** and use the section tabs. Each section maps to one Mibyan Cloud service.

<Tabs>
  <Tab title="Ship" icon="rocket">
    | Section | What it does |
    | - | - |
    | **Overview** | Live deployment and the Mibyan Cloud services connected to this app |
    | **Versions** | An immutable history of every production deploy, with instant rollback to a previous ready version |
    | **Previews** | Temporary links that share a fixed version for viewing only, without giving access to the project |
    | **GitHub Sync** | Two-way sync of the app source with protection for changes on both sides, and an audit log |
    | **Domains** | Track DNS proof and TLS certificate preparation before the domain counts as live |
  </Tab>

  <Tab title="Data and users" icon="database">
    | Section | What it does |
    | - | - |
    | **Database** | The active schema, tables, and access policies the app uses |
    | **App users** | Sign-up and sign-in policy for the app's own users, fully separate from Mibyan account holders |
    | **Storage** | Durable file buckets with their own permissions and limits, independent of the sandbox and the published build |
    | **Realtime** | A change feed with a cursor and permissions that match the app's data |
  </Tab>

  <Tab title="Backend" icon="server">
    | Section | What it does |
    | - | - |
    | **Backend functions** | Versioned functions run in an isolated runner with a timeout and a network policy |
    | **Backend secrets** | Write-only encrypted variables injected into production functions only at run time |
    | **Integrations and webhooks** | Connect n8n, Make, or Zapier to app events through durable, signed deliveries that retry |
  </Tab>

  <Tab title="Messaging and money" icon="credit-card">
    | Section | What it does |
    | - | - |
    | **Transactional email** | Safe templates sent to the authenticated user themselves, with rate limits and no open relay |
    | **SMS** | Encrypted templates sent only to the authenticated user's own number, with one-time codes and rate limits |
    | **Payments** | Connect Paddle directly, then manage the price catalog from the agent or app settings |
    | **Analytics** | Anonymous usage events and a 30-day summary, without storing raw IP addresses |
  </Tab>
</Tabs>

<Note>
  App users are separate from your Mibyan account. The sign-up and sign-in policy for your app's users is managed on its own, apart from the accounts of Mibyan owners.
</Note>

## Publishing safely

<Steps>
  <Step title="Preview first">
    Check the running app in the preview. Share a **preview link** for feedback: it shows one fixed version and does not grant project access.
  </Step>

  <Step title="Publish">
    Ask the agent to publish, and the app goes live. Each publish is stored as an immutable version.
  </Step>

  <Step title="Verify the domain">
    To use your own domain, add it, create the DNS record shown, and wait for verification and the TLS certificate. The domain is treated as live only when both are ready.
  </Step>

  <Step title="Roll back if needed">
    In **Versions**, restore an earlier ready version instantly if a release goes wrong.
  </Step>
</Steps>

## Working as a team

In **Team**, invite existing Mibyan members and choose their permission: **view**, **edit**, or **deploy**. You can also see who is online in the app right now.

## What the agent can do for you

Because the App center mirrors what the agent can configure, you can do either. The agent can set up the database schema, sign-in policy, storage, backend functions, email and SMS templates, the payment catalog, a custom domain, and GitHub sync; check the status of each; publish; and roll back.

<Warning>
  Publishing, changing DNS, and payment or messaging setup have real-world effects. Review what the agent proposes before you approve it, and keep secrets in **Backend secrets**, never in the app's code or in chat.
</Warning>

<Card title="Next: connect data and tools" icon="plug" horizontal href="/products/connectors">
  Connectors and the marketplace let agents work with your databases and services.
</Card>