Managing app data

Sharing a backend

Learn how to build and manage multiple MeDo apps that share one backend, including shared resources, billing, and a practical multi-channel example.

Updated 2026-09-11

#Overview

One set of data, several apps in front of it. Instead of giving every app its own database, you point a new app at an existing project's backend, so they read and write the same records. A customer website, a staff dashboard, and an owner app can share customers, products, and orders while each keeps its own pages and design.

#When to use a shared backend

Whenever several apps serve the same users or the same business process:

• E-commerce: a storefront and a merchant dashboard share products, customers, and orders.
• Business operations: an employee app and an admin dashboard share accounts, permissions, and workflows.
• Content platforms: creator tools and a reader-facing site share published content and engagement data.
• SaaS products: a customer app and an operations dashboard share tenant and subscription data.
• AI products: a website and a mobile app share user accounts, saved outputs, and usage records.

#Create an app on a shared backend

1. On the Home page, describe the new app in the prompt box and pick its type (for example Website or Mobile).
2. Click Shared Backend under the prompt box and choose the project whose backend you want to reuse.
3. Send the prompt. Mention the sharing in the text as well — "using the same backend as the restaurant ordering website" — so the requirements document is built around the existing tables.
4. Review the requirements document, especially the Backend tab, and click Generate App.

The new app uses the selected project's database, storage, sign-in, and functions. Its frontend is separate, so you can design it for a different audience or device without touching the other apps.

#Manage apps that share a backend

On the Project page, the Shared Backend tab groups every project that shares a backend, so you can find related apps and check each one's backend status. Each app is still its own project: publishing, access, credits, and settings are per app.

Changes to shared tables or functions affect every connected app. Before removing a field, changing a permission, or altering a function, make sure the other apps no longer depend on it.

#What is shared

Apps on the same backend share:

• Database: table structures and business data, such as users, products, and orders.
• Storage: uploaded files and other stored assets.
• Auth: sign-in configuration and user accounts for a consistent identity system.
• Backend Functions and Secrets: server-side logic and the keys it uses, callable from every connected app.

For example, a customer website, an admin dashboard, and an owner app can all work with the same customers, menu items, and orders. An order placed on the website can appear immediately in the admin dashboard and contribute to the metrics shown in the owner app.

#Billing

Sharing a backend does not merge the bills. Each app with its backend enabled pays its own daily backend fee — 15 credits per app per day at the basic size — so three apps on one backend are three backend charges. Skills are also configured and billed per app. See Credit System.

#Worked example: restaurant ordering across three apps

Three apps on one backend cover a complete restaurant workflow:

• Customer website: customers browse the menu, place orders, and track order status.
• Admin dashboard: staff process orders, update statuses, and manage menu items.
• Owner app: the owner monitors sales, order activity, popular items, and pending work.

All three apps use the same customers, menu items, orders, and operational data.

#Step 1: Build the Customer Website

#Prompt

Build a restaurant ordering website where customers can browse menu items by category, customize options and add-ons, add items to a cart, place an order, and view order history with New, Preparing, Ready, and Completed statuses.

#Features

• Menu browsing and categories
• Item options and add-ons
• Cart and checkout
• Order history
• Order status tracking
• Reorder from a previous order

#Step 2: Build the Admin Dashboard

Start a second app from the Home page, click Shared Backend, and choose the customer website's project.

#Prompt

Using the same backend as the restaurant ordering website, build an admin dashboard for staff. Include administrator sign-in, order filtering by status, order status updates, menu item management, today's order count, and today's revenue.

#Features

• Administrator sign-in
• Order list and status filters
• Order status updates
• Menu item management
• Today's order count
• Today's revenue

#Step 3: Build the Owner App

Start a third app the same way, sharing the same project.

#Prompt

Using the same backend as the customer website and admin dashboard, build an owner app. Show today's revenue, order volume, best-selling items, pending orders, sales and order trends, and new-order alerts.

#Features

• Business overview
• Today's revenue and order volume
• Pending orders
• Best-selling items
• Sales and order trends
• New-order alerts