We chose open, established and well-documented technologies so you can decide how and where to run your apps. Apps remain PocketBase projects, data stays in SQLite files, and moving the engine takes a folder copy.
Go is an open-source language introduced by Google in 2009 for building reliable network software. Docker and Kubernetes are also written in Go.
For Pyrite, that means one executable, with no separate runtime, dependencies or installer. Copy the folder and run it. The same source code already compiles for Linux.
PocketBase is an MIT-licensed, open-source backend written in Go. One program provides a database, user authentication, file storage, REST and realtime APIs, and an admin dashboard.
Pyrite uses PocketBase twice: as the foundation for the engine and as a separate instance for every app that stores data. App logic lives in readable, portable JavaScript hooks and migrations. The PocketBase version is fixed and tested, currently 0.40.6: a new version arrives only with a Pyrite update.
SQLite stores an entire database in one file. The application reads and writes the file directly, with full transaction support. There's no database server to install or maintain. If the power fails during a write, the data stays consistent.
SQLite is the world's most widely used database, found in smartphones and web browsers. Its authors have committed to keeping the file format compatible through 2050, and the US Library of Congress lists it among the recommended formats for long-term data preservation.
For Pyrite users, backups amount to copying files, and dozens of tools can open the data even without Pyrite. SQLite handles one write at a time. That suits most web apps, though high-volume online services can have heavier write workloads than it is designed for.
Apps communicate over HTTP using JSON, logic is written in JavaScript, and code and data live in ordinary files on disk.
With this stack, moving your data can be as simple as copying a file.
Every app that stores data keeps its records in a SQLite database inside its data folder. There's no database server to query or export from.
Download an app backup from the console. It contains the database and files that people have uploaded. You can do it yourself, in standard formats.
Put the data into a PocketBase instance running the same version, currently 0.40.6. Your collections, records, files and users are all there.
When you choose to leave, we'll provide a complete package: your app repackaged as a standalone PocketBase project, with its pages, rules, data and sign-in.
We want to earn your trust by using open technology, keeping data accessible and making sure you can always move your apps elsewhere.
You can inspect the source code, choose where your SQLite files live and run the engine on your own servers, even offline. You don't need an account with a hosting provider to run your apps.
If you ever want to change course, the way out is always open: your apps stay PocketBase projects and your data stays in SQLite files. Staying or leaving is your choice, not a dependency.
Code and data live in separate folders. The engine stages a new version alongside the running one and switches only after every check passes.
This applies to hosted apps and to the engine itself, which saves a copy of its registry before every update.
We wrote a skill for AI agents: a public document in English and Italian that the agent reads before writing any code. The result is a standard PocketBase app with security rules in place, ready to run on the engine.
app.json manifest, migrations, hooks and pages. It uses the same layout as any other PocketBase project.