Studio Help

Connecting the Mudbase backend

When you build your first app in Studio, a Mudbase backend project is provisioned for it automatically. This gives your app a real backend with no setup on your part.

What the backend includes

  • Authentication: Users can sign in with email and password, magic link, or social login. Session management and password reset are built in.
  • Database: A document database for storing your app's data. You define the structure through your app or through the Mudbase console.
  • File storage: Upload and serve images, documents, and other files. The SDK handles permissions.
  • API: A REST API that your app calls through the Mudbase SDK. You can also call it from other tools or apps.

How Studio connects to the backend

The Mudbase SDK is included in every Studio app. When Studio generates code that reads or writes data, signs users in, or uploads files, it calls the SDK which talks to your backend. You do not need to write connection code.

Viewing and managing your backend

Your backend is separate from Studio. You can see and manage it in the Mudbase console at console.mudbase.dev. From there you can:

  • Browse and edit your database collections.
  • Manage users and permissions.
  • View file uploads.
  • Generate and revoke API keys.

Using the backend from outside Studio

Because your backend is a standard Mudbase project, you can call its API from any other front end, mobile app, or script. Get your project's API key and base URL from the Mudbase console.

What happens to the backend if you delete a Studio project

Deleting a Studio project also deletes the associated Mudbase backend, including all the end-user accounts, data, and files your app created. If you want to keep the backend, transfer it to your own Mudbase account first (available from the project overflow menu) before deleting the Studio project.

Chat with us