Add a backend to your app
Enable managed data, sign-in, file storage, and secure server-side features when your app needs them.
Enable Ahamo's managed backend when your app must remember information, recognize people, keep uploaded files, or run trusted work away from the browser. A brochure site or calculator may not need one; a booking flow or private dashboard usually does.
What the backend adds
The backend gives an app managed building blocks for:
- structured data, such as bookings or profiles;
- sign-up, sign-in, and sessions;
- files uploaded through the app;
- server-side functions for permission checks and controlled updates.
Runtime exposes inspection views for the capabilities the app uses, including data, auth, storage, functions, deployments, logs, and health. Ahamo must still build the forms, rules, and screens that use them.
When to enable it
Ask four questions:
- Must something still exist after the visitor closes the page?
- Does the app need to know who the visitor is?
- Will a visitor upload a file?
- Does an action require a trusted permission check?
If any answer is yes, describe the smallest complete journey first. Save and display one booking before adding accounts, staff roles, reminders, and reporting.
Enable it and confirm readiness
Open the app and choose Runtime. When Ahamo presents the backend requirement, choose Enable backend and wait for provisioning. A ready Runtime shows the managed environment and its Overview, even before tables or users exist.
Then ask Ahamo to build one feature against it:
Save each completed booking with its service, date, time, customer name, email, and status. Show the saved details on the confirmation page and a clear error when saving fails.
Complete the booking in preview. In Runtime, select the relevant environment, open Data, and find the row. Refresh the app and confirm it reads the booking back.
Runtime can report Development, Staging, and Production, depending on what is available for the app. Always check the selected environment and the data-authority notice. Development and production may be separate, or the interface may identify shared live data; never infer the boundary from an environment name alone.
Use fictional information while testing. Do not put passwords, session values, customer records, or provider credentials in the conversation. Add access rules before private data is exposed, and verify those rules with a signed-out visitor and a second account.
Next: Add a database or add sign-up and sign-in.