Build an App with a database and user accounts
Your App can save information, recognize users, and handle uploads. Eazo provides the backend foundations, so you can describe the experience without knowing how to build a backend yourself.
| id | user_name | title | status | created_at |
|---|---|---|---|---|
| 1042 | Alex Chen | Website update | in_review | 2026-10-21 |
| 1041 | Alex Chen | New project brief | received | 2026-10-20 |
| 1040 | Sam Rivera | Launch checklist | complete | 2026-10-18 |
Add a database and user accounts to your App.
Apps with accounts, saved data, or uploads need more than screens. Eazo helps build that backend from your description, so you can focus on what the App should do for people.
Use a managed backend without setup
Use Eazo’s managed database, sign-in, and file storage without setting up separate services or connection keys.
Build server-side App logic from a prompt
Tell the Agent what users can save, upload, and see. It builds the server-side logic that connects those actions.
Keep App data available across visits
A backend keeps records available after refresh and gives returning users access to the right information.
Keep App data, users,
and files connected.
Your App can keep a request, recognize who sent it, and hold on to the files that belong with it. These three capabilities work together when your App needs them.
Save App data across visits.
Requests, tasks, and progress can still be there when someone opens the App again.
Recognize signed-in users.
Give each person a view of the records and updates they are allowed to see.
Project brief and reference files
Store files with App records.
Documents and images stay connected to the record they help explain.
Illustrative App screens showing how the capabilities work together.
Database, authentication,
and file storage.
Each capability has a different job. Use the ones your App needs and tell the Agent how people should use them together.
Save App records in a managed database.
Describe the information people create or change. The Agent can design records and connect the App’s actions to a managed database.
How data and files work- Tasks and learning progress
- Requests and orders
- Community posts and preferences
Add user authentication and sessions.
Eazo provides identity and session foundations. The Agent adds a sign-in flow when the App needs accounts, private records, paid access, or payments.
How sign-in works- Recognize a returning user
- Connect records to their owner
- Support private or role-based views
Store uploaded images and documents.
Add avatars, images, documents, or attachments. Object storage provides a file URL that the App can save with a related record.
Read the file storage guide- Profile images
- Documents on a request
- User-created media
App examples with saved data and sign-in.
Then describe the people, records, and access rules involved. These are a few ways to put the foundations together.
“Build a request tracker. Customers can sign in, submit a request with an attachment, and see only their own requests. Staff can review and update all requests.”
Personal dashboard
Save tasks or progress and show each person only their own history.
Service requests
Connect an order or request to the customer, its status, and supporting attachments.
Learning community
Keep contributions and progress across visits, with clear rules for public and private content.
Frequently asked questions about databases and sign-in.
When does my App need a database or sign-in?
Use a database when information must survive a visit, and add sign-in when records or access belong to a particular person. A public calculator may need neither; a dashboard, membership, order, or progress tracker usually needs both.
Do I need to set up my own database, storage, or authentication provider?
No for these Eazo built-in capabilities. Describe the data, file, and sign-in flows you need. The Agent connects them without asking you for a separate database connection, storage key, or authentication-service account.
Does every App require its visitors to sign in?
No. A purely public display App may not need a sign-in interface. Keep sign-in when the App stores private per-user data, restricts paid access, or accepts payments. In Eazo Mobile, Apps normally recognize the signed-in Eazo user; in a standalone browser, available sign-in methods depend on the generated interface.
Is each user’s private data kept separate?
That requires server-side access checks tied to the signed-in user. A sign-in screen or a filtered list alone does not prevent someone from requesting another person’s records. Test with more than one account before publishing a private workflow.
Who can access the data stored by my App?
That depends on the access rules built for each flow. Public content can be readable without an account, while personal or administrative records should require the appropriate signed-in user or role.
Can users upload images, documents, or other files?
Yes. The Agent can connect file uploads to object storage and save the file URL with its related record. State accepted types, size limits, and who may upload or retrieve each file.
Does a private record make its attached file private?
Not automatically. An object-storage URL may be publicly accessible even when its related record is private. If the file is sensitive, specify that only authorized users may view it and verify the protection in the finished App.
Can I view the App’s database in my Project?
The Database area appears after the Project has a managed database and lets you inspect saved data. Database viewer access depends on your current plan; check the Pricing page for plan details.
What happens to existing data when I change the App?
Interface changes do not need to replace saved records, but changing fields or relationships requires care. Tell the Agent what existing data must be preserved, review the migration plan, and test the affected flows before publishing the update.
Can I import existing data or export it later?
Import and export requirements depend on the App and data shape. Describe the source format and the records you need when you start or update the Project so the Agent can build a deliberate transfer flow instead of relying on manual copying.
What happens when the App grows to more users or more data?
Review slow queries, storage use, authorization rules, and the busiest user journeys as usage grows. The first generated version is a starting point; production data flows should be tested and refined like the rest of the App.
Make an App worth coming back to.
Save what matters, give each user their own space, and let them pick up where they left off.
Build an App with data