Apps
What runs on ASafariM OS, and the products built alongside it: every place you can reach each one, and how far it is.
Built into the OS
-
Identity
One sign-in for every app
Sign in once with an email code, a passkey or Google, and every OS app knows who you are. Someone new asks for access to the apps they need, with a note, and an admin approves.
-
Web app
id.asafarim.site
Live
Sign-in, your account and access requests.
-
Web app
id.asafarim.site
Live
-
Docs
Read your documentation, take notes
A private reader for documentation repositories: read the Markdown, keep study notes on it, and turn a note into a GitHub issue in the repository that owns the document.
-
Web app
docs.asafarim.site
Live
For people an admin gave a Docs role.
-
Web app
docs.asafarim.site
Live
-
Flow
Workflows that run on events
Build a workflow visually, start it from an OS event, a webhook or GitHub, and let people approve or reject a step before it goes on. Six connectors, an encrypted credential store, and drafts written by Claude from an issue, which never run by themselves.
-
Web app
flow.asafarim.site
Live
For people an admin gave a Flow role.
-
Web app
flow.asafarim.site
Live
-
Admin
Run the OS
Installed apps and their state, roles and grants, access requests, and one audit centre for sign-ins, access decisions and admin changes.
-
Web app
admin.asafarim.site
Staff only
For admins only, so it is not linked here.
-
Web app
admin.asafarim.site
Staff only
-
Notes
The reference app
The smallest app that shows the contract end to end: a manifest, its own database, registering itself, sign-in through Identity, roles granted by an admin.
-
Example
Local development
In development
Runs in the dev environment; not deployed.
-
Example
Local development
In development
Products built by ASafariM
Their own code and domains, with the OS's look; their project pages are served by the OS stack.
-
IGS-Pharma
An online pharmacy for Belgium
Built with a Belgian pharmacy: a webshop for non-prescription products with a pharmacist in the loop, a back-office for the pharmacy team, and a free Android app. Its own code and domain, with the OS's look; the project page is served by the OS stack.
-
Website
igs.asafarim.site
Live
The project, in Dutch, French, German and English, with the app's privacy pages.
-
Webshop
igs-pharma.be
Early access
Closed until launch: customers the pharmacy invites or approves see it already.
-
Android app
Google Play
Testing
Browse, search, scan a pack and keep a list; orders go to the webshop. In internal testing.
-
Back-office
Pharmacy staff
Staff only
Catalogue, prices, stock and recalls, orders, delivery and early access, behind a passkey.
-
Website
igs.asafarim.site
Live
-
Breinhap
Short study missions for secondary school
A study app for Flemish secondary-school students, designed with ADHD and AuDHD in mind: missions of 2 to 6 minutes, always in the same four steps.
-
Android introduction
breinhap.asafarim.site
Live
What the app is, in Dutch and English, with its privacy pages.
-
Web app
breinhap.com
In development
Public introduction and adult login/register entry pages; browser missions are not available yet.
-
Breinhap management
management.breinhap.com
Early access
Invitation-only pilot for active ASafariM adults with explicit Breinhap access.
-
Android app
Google Play
Testing
In a closed test before it opens to everyone.
-
Android introduction
breinhap.asafarim.site
Live
-
Observatory
Your development workspace, in perspective
Explore saved Git workspace observations, repository changes and history. Evidence-linked AI summaries help explain the metrics. Every registered ASafariM account can view; approved admins can refresh the view and generate summaries.
-
Web app
observatory.asafarim.site
Live
Sign in with ASafariM. Viewer access is included; admin tools require approval.
-
Web app
observatory.asafarim.site
Live
Shipped
What is built and merged so far, phase by phase.
-
P0
Foundations
The workspace, CI and the self-describing app contract: an app's manifest, its validator and JSON Schema, and the platform CLI that compiles manifests and checks that the core never imports an app.
-
OS-D1
Local dev environment
One command starts the whole OS locally: Postgres, Redis, identity, core-api, a dev login stub with seeded users, and a dev gateway in front of every app.
-
P2
Identity
The OpenID Connect provider for id.asafarim.site, with sign-in delegated to Hub, plus its published container image and production deploy files.
-
P3
Control plane
core-api's registry, permission catalog and lifecycle; the app SDK and Notes, the first built-in app; the Admin console for apps, roles, grants and the audit log.
-
P4.1
Event bus and bus auth
NATS JetStream with CloudEvents, an outbox and relay, durable consumers with dedupe and dead letters, and per-app bus permissions checked by core-api when an app connects.
-
P4.2
Event catalog
Apps upload signed schemas for the events they publish, and the Admin console lists every event type with its publisher, subscribers and schema.
-
Remove
Remove an app
The last lifecycle step: an admin removes an app, its grants and bus resources are cleaned up, and it can be installed again from scratch.
Merged pull requests: #69
-
P6.1
Health and status board
core-api checks every active app's live and ready endpoints from its manifest, and the Admin console shows them on one Status page.
Merged pull requests: #84
-
Landing
This page is live
asafarim.site now serves the OS landing page from its own container, deployed on its own with one command and no identity. The placeholder page is gone.
-
P6.2
Traces, request metrics and trace-id logs
Every app's requests become OpenTelemetry traces and per-route rate, error and duration metrics, with only route patterns leaving the app, and its JSON log lines carry the trace id. One command starts a local collector.
Merged pull requests: #96
-
External apps
Install an app from its image
An app built in another repository is installed from its container image: its manifest travels as an image label and is validated, and one command runs it locally or writes its production compose file.
-
Docs
A private documentation reader
docs.asafarim.site, the second built-in app: it renders documents from their source repository with contents and search, keeps study notes on a part of a document, and is open only to the people the OS grants it to.
-
P6 part 2
Traces across apps
One request stays one trace through the gateway, core-api and the event bus, and every app flushes its traces and metrics when it stops.
-
Retention
Backup and purge
Removing an app first backs up its database. The database is dropped only after a retention window, and only if the backup is still there and unchanged. The CLI can remove, purge and list them.
-
P7.2
Manifest review
Every pull request gets an advisory check that compares an app's manifest with its code: unguarded routes, permissions never checked, and events without a schema or a handler, posted as one comment.
-
Sign-in
Email codes and passkeys
id.asafarim.site signs people in with a one-time email code or a passkey, built in the OS with no outside provider, and an admin approves new connections.
-
P7.4
Event search
The Admin console's event catalog answers questions like "which app emits something when an order ships?" by searching event types, apps and schema descriptions.
-
Database spans
Database time in every trace
Queries from core-api, Notes and Docs show up in their request's trace with the operation and the database name only, never the SQL text or its values.
-
Top bar
App switcher and account menu
Every OS app has the same top bar: a switcher to each app you can open, and an account menu with your name and Sign out.
-
Core in production
core-api and its own database
core-api runs in production next to the OS's own Postgres on a private network, started by the deploy only once its encrypted settings are committed. A failed image pull is retried before the deploy gives up.
-
Alerts
Down and recovered alerts
core-api can send one message to a chat webhook when an app goes down and one when it recovers. It keeps the history on the Status page, and remembers what it already reported across a restart.
Merged pull requests: #150, #154, #158, #159, #160, #161, #163
-
P7.1
Scaffold a new app
One command writes a new app with its manifest, sign-in, the OS top bar, a permission-checked example route, health endpoints, telemetry and a test. It passes manifest review with no findings.
-
Admin live
Admin console in production
The Admin console runs at admin.asafarim.site: admins manage apps, roles, grants and the audit log there.
Merged pull requests: #176
-
CLI
The OS from the command line
The platform CLI reads what the Admin console shows: the audit log, every app and its state, one app's permissions and roles, who holds which role, and the event catalog with its keyword search.
Merged pull requests: #172, #177, #178, #179, #180, #181, #182
-
Retention part 2
Backups checked on demand
A removed app's backup can be verified at any time, from the command line or from the Admin console's Apps page, before its database is purged.
-
Look
One look for every app
One light and dark theme with a toggle in every header, data tables that fit a phone, a shared layout for the sign-in pages, and a link to the Admin console for admins.
-
Sister sites
Breinhap and IGS-Pharma
The OS stack also serves the landing pages of two ventures built in their own repositories, breinhap.asafarim.site and igs.asafarim.site, linked from every OS navigation.
Merged pull requests: #209, #210, #212, #219, #224, #228, #229
-
Legal
Privacy, cookies and terms
Privacy, cookie and terms pages linked from every OS footer, and a sitemap, share preview and structured data for this page.
-
Sign-in part 2
Continue with Google and access requests
id.asafarim.site adds Continue with Google next to email codes and passkeys, with redesigned sign-in pages. A new person asks for access to the apps they need, with a note, and an admin approves.
-
Audit centre
An audit centre
The Admin console shows sign-ins, access decisions and admin changes in one audit centre.
Merged pull requests: #248
-
Flow
Flow, the workflow app
flow.asafarim.site, the third built-in app: workflows that run on events, with approval steps a person approves or rejects. Its first workflow has the Docs app draft a GitHub issue and creates it once someone approves.
Merged pull requests: #249, #250, #251, #254, #255, #257, #258
-
Bus in production
The event bus in production
NATS joins the production stack, and core-api, Docs and Flow connect to it when it runs.
-
Sessions
One sign-out everywhere
An app's session ends when the identity session does, and signing out of an app also ends the id.asafarim.site session. A test fails if the two lifetimes drift apart.
-
P7.2 part 2
A deeper manifest review
Manifest review catches many more mismatches between an app's manifest and its code: secrets, config and permissions declared but never used or used but never declared; routes, health paths and launcher tiles nothing serves; events and schemas that don't line up; database gaps; and names or ports that clash. The CLI's README lists every finding, and a test keeps the list complete.
Merged pull requests: #184, #188, #189, #190, #191, #192, #193, #196, #197, #198, #199, #200, #203, #208, #211, #213, #220, #221, #222, #223, #226, #227, #230, #231, #232, #236, #237, #238, #239, #241, #242, #244, #246, #247, #263, #264, #265
-
Flow slice 2
The workflow builder and connectors
Flow gets a visual builder, a new workflow format and the engine that runs it, webhook and GitHub event triggers, six outbound connectors, and an encrypted credential store behind an allow-list of the hosts it may reach.
-
Switcher
A new app switcher
An icon-only app switcher in every app, one menu open at a time, and a launcher panel that a host page's styles can't break.
-
Flow files and AI
Workflow files and drafts from issues
Workflows can be exported, printed and imported as files. Flow can also draft a workflow from a GitHub or GitLab issue with Claude: the draft never runs by itself, and every step that sends data out arrives unconfigured.
-
Flow hardening
Flow, hardened
Pause all stops work already in flight and fails closed. The public webhook endpoint answers unknown and forged calls the same way and limits floods per source, and credentials stay bound to their settings.
Screenshots
Taken by Playwright from the end-to-end test environment, not drawn by hand.
Roadmap
-
P4
Events, finished
A read-only live demo of core-api, Admin and Notes, and TLS and operator mode for the event bus, now that it runs in production.
-
P6
Observability
Metrics, traces and logs in one place with dashboards, alerts on traces and metrics, and a public status board.
-
P7
AI assist
AI help where text matching can't see: drafting a new app's manifest, a deeper manifest review, semantic event search and a read-only copilot in the Admin console.
-
Flow slice 3
Scheduled workflows
Workflows that start on a schedule, and new workflows that run as a dry run first.