Portable
Layers and roles are abstracted so you swap firewall, identity provider, database, AI provider, and hardware family without re-architecting; nothing is wired to a single vendor or chip family.
Beelab is not a third-party-certified product. PARSO-SAMAD is the internal framework used to grade every release against ten engineering pillars on a 5-point scale, totaling 50 points. The framework was originally written in 2025 and is published here so you can audit how Beelab grades itself.
Can I unplug it, move it, and restore in 15 minutes?
Will it run for two weeks without me touching it?
When did I last test a full restore?
What can an attacker do with my public IP?
How do I know it's healthy right now?
Can I add a service without breaking something else?
Can I prove who changed what and when?
Will I understand this config in three years?
What's my actual uptime?
Will this hardware last five or more years?
Scored per release, published in changelog.
Total points across the ten pillars place a release in one of five bands. The label below the score on this page is the band the current total falls into.
Last self-assessed: 2026-05-17. Next assessment: per release. Per-pillar breakdown ships in the next changelog entry.
PARSO-SAMAD is Beelab's own self-assessment framework. It is not a third-party audit, certification, or attestation. Your organization remains the data controller, processor, or covered entity as applicable for SOC 2, HIPAA, GDPR, or any regulated workload you run on Beelab.
Evidence
One layered, public-safe sentence per pillar, self-assessed against the framework above and dated so you can check the work against /changelog when a new release ships.
Layers and roles are abstracted so you swap firewall, identity provider, database, AI provider, and hardware family without re-architecting; nothing is wired to a single vendor or chip family.
Provisioning, deploy, backup, and monitoring run on declarative manifests with a GitOps default (Forgejo + ArgoCD or your choice), so rebuilding the stack from code is the steady state, not the exception.
Backups (encrypted snapshots and offsite copy to a provider you pick) plus a written restore drill are part of the platform contract, not an afterthought; restore steps live in the runbook next to the backup config.
Zero-trust networking, single sign-on with MFA (Authentik or your identity provider), secrets in a vault, encrypted at rest and in transit, with a published responsible-disclosure policy at /security.
Metrics, logs, uptime, and alerts ship wired in through an observability layer (Prometheus, Grafana, Loki, Uptime Kuma defaults, swap any piece), so the platform tells you it is healthy before you have to ask.
Compute scales 1 to N nodes or N racks across multiple cluster types coexisting side by side (immutable Kubernetes, lightweight Kubernetes, virtualization, container workloads, and the Apple Silicon AI mesh).
Every release carries a PARSO-SAMAD self-assessment and a public record on /changelog and /roadmap; the rubric, the score, and the date are all visible on this page.
One job per node, one node per job, blast radius bounded by role, with routine ops, upgrades, and migrations captured as documented playbooks you can read before you touch anything.
Public surfaces target WCAG 2.2 AA on color contrast, focus visibility, and motion; admin surfaces accept keyboard and screen-reader workflows alongside pointer input.
Validated hardware families (HP EliteDesk, Lenovo ThinkCentre, Dell OptiPlex, Minisforum, Mac mini Pro, Mac Studio), ECC where supported, ZFS mirrors, and redundant power and network paths on the parts that matter.