01 / Product

One program, two jobs.

Pyrite manages all your apps and runs each app that stores data in its own PocketBase instance. Administrators use the console, people use the portal to open their apps, and the engine connects the two.

“One console to manage your apps. One portal to use them.”

The product in a nutshell

02 / The console

Manage every app from one console.

Open the console in a browser at the engine's address. Only Owners and Admins can sign in, using their directory accounts. Each sees what their access level allows.

02.1Overview: App status, resource usage, traffic, ongoing operations, recent events and apps awaiting approval, all on one page.
02.2Applications: See every app and its status. Each app has its own page for access, roles, data, imports and settings.
02.3Upload app: Install an app from a ZIP file. Follow the checks as they run and review the summary. If an Admin uploads the app, an Owner must approve it.
02.4People and groups: The central directory lists people, groups and the apps each can access.
02.5Backup: Create, download and restore backups of the engine and its apps. Nightly backups run automatically.
02.6Engine history: The engine's log records starts, stops, errors, backups, restores, sign-ins, changes and approvals, in a file that nobody can delete from the console. By default it keeps them for one year.
02.7Analytics: See who's been using each app over the past 30 days, how much they've used it, when each person was last active and which permissions need review.
02.8Tools: Explore the tools the engine provides, including Excel and CSV imports, and see which apps use them.
02.9Portal home: Customize the page people see when they sign in and preview it before publishing.

03 / The portal

One way in for everyone.

The portal lists your apps at the engine's address. Sign in once with your email and password. Select any tile to open its app, already signed in. Signing out ends the session across all apps.

Apps open to everyone are visible even before sign-in. Anyone signed in to the portal can use “Import preview” to upload an Excel or CSV file and preview how it will be read. No records are imported, so people can prepare their data before handing it to the administrator.

04 / The lifecycle

From the first release to the archive.

Every app follows the same steps in the same console.

Create or uploadCreate an app folder in the console, or use “Upload app” to submit a ZIP built to the standard.
ApproveNew apps are installed but left stopped. The administrator reviews the manifest and code, grants access and starts the app.
MonitoringThe engine runs a health check every five seconds, restarts the app if it fails and records metrics every minute. It keeps 30 days of history.
UpdateReplace the code without touching the data. A package update either completes in full or leaves the existing version in place.
ArchiveWhen an app is no longer needed, the engine copies it to the archive and verifies the copy before freeing up its folder.

05 / Apps

Three types of app.

An app's type describes its contents. Access is configured separately, so even a simple collection of pages can be restricted to a few people.

05.1

Static

What's inside: The engine serves static HTML, CSS and JavaScript files without an instance or database. The same access controls apply as for other apps.
Examples: A guide, a calculator, a directory updated with each release of the app, or a website.

05.2

With a database

What's inside: A dedicated PocketBase instance with collections, record-level access rules, JavaScript hooks and migrations, and REST and realtime APIs.
Examples: A studio's bookings, a shop's catalog or the example app's spare-parts price list.

05.3

With automation

What's inside: A database app with scheduled jobs (cron) running inside its instance for tasks such as fetching data or processing repetitive work.
In the console: The engine runs it like a database app. The Scheduled jobs page shows when each job runs and how its last run went, with Pause and “Run now”.

Download the alpha Administrator guide