Separate databases
Keep each project in its own SQLite database, with independent schemas, users, access rules, service keys, and backups.
Host isolated SQLite databases, publish web applications, and build no-code interfaces from one backend. Each database has its own collections, application users, access rules, REST API, functions, and backups.
Explore Takhzeen ↓takhzeen.manhaj.dev| id | name | type |
|---|---|---|
| 01 | Something useful | web app |
| 02 | The next idea | database |
Keep each project in its own SQLite database, with independent schemas, users, access rules, service keys, and backups.
Work with records through a namespaced REST API and realtime event stream. Define collection rules for who can read and change records.
Use a drag-and-drop app builder with pages, forms, record lists, detail views, login, and containers. Bind interfaces to your database collections.
Upload a static site bundle or push to a database’s Git repository. Serve an existing build or configure a build runner to build on push.
Extend your application with WebAssembly functions and scheduled jobs, alongside the built-in database and authentication services.
Use the integrated administration dashboard for collections, accounts, application settings, and hosting. The backend and dashboard run from one executable.
Takhzeen hosts static frontends. Server-side application runtimes are not executed as uploaded sites; use its Functions capability for backend logic.
Explore the rest of our software collection.