Operate
Run background jobs on a durable queue, schedule them with cron, and see every run in one history.
Bosca System
System is the operating layer underneath Bosca — durable background jobs and scheduling, identity and access, object storage and backups, the datastores it all runs on, and the settings that tie it together. In one place.
How it works
Run background jobs on a durable queue, schedule them with cron, and see every run in one history.
Principals, groups, and permissions; passwordless passkeys, OAuth sign-in, and scoped API tokens.
Change how the platform behaves without a redeploy, and bring in the outside services you already use.
What's under the hood
The jobs, the scheduler, the identity model, storage, and backups — the machinery your platform runs on, in one place.
Background work on NATS JetStream or Redis, with at-least-once delivery and automatic retries.
Scheduled jobs on standard cron, with catch-up for missed runs and a full run history.
A report over your content graph — published items pointing at unpublished ones, and more.
One identity behind every profile, device, and token; permissions granted to flat groups.
Passwordless WebAuthn sign-in, plus OAuth with Google, Apple, and more.
Programmatic tokens scoped within a principal's permissions, for scripts and CI.
Snapshot Postgres and your files to one archive, and restore with a conflict strategy.
Cache, job queue, and object storage sit behind interfaces — Redis or NATS, S3 or GCS, your choice.
Content health
Most admin panels watch connections and memory. Bosca's health check reads your content graph and flags what publishing can miss — a published page pointing at an unpublished document, a guide with steps that never shipped, a collection with hidden children, a schedule that came and went. Some it can fix on the spot.
Pluggable by design
Bosca's services sit behind interfaces, so you're not bolted to one vendor's stack. The job queue, the cache, and pub/sub each run on Redis or NATS. Object storage is S3, Google Cloud, or the filesystem — or anything S3-compatible. Swap a backend, and the code that uses it never notices.
Go deeper
Jobs, scheduling, identity, storage, backups, and configuration — the operating layer that keeps Bosca running.