Hosted dedicated instance
A managed deployment run for your organisation alone — dedicated database, dedicated application, TLS at your own hostname. No infrastructure on your side.
Deployment
One organisation per deployment.
SPARC is not multi-tenant SaaS. Cross-organisation tenancy is excluded by a ratified architectural decision — your instance holds your data and nobody else's.
Self-hosted
The same containerised stack deployed inside your own environment for defence and IP-sensitive programmes — Docker Compose, PostgreSQL, a reverse proxy. Standard infrastructure.
The public evaluation instance at app.sparcplatform.uk runs this exact stack.
Security controls.
As they exist today.
- Invite-only access — accounts exist because an administrator created them.
- Non-disclosing authentication — a failed sign-in returns the same response whether or not the account exists.
- Per-IP rate limiting on authentication endpoints.
- Append-only audit trail with before/after state on every change.
- Scripted database backups with a documented restore path.
Current limits.
Each gap is listed with its state, in the same three-state convention used across this site.
Protective marking
RoadmapNo classification banner or marking ceiling exists today. The specified design — markings across every document producer and a fail-closed instance ceiling — is written and awaiting ratification.
Per-account lockout
RoadmapRate limiting is per-IP today. A per-account lockout is queued and not built — no lockout counter appears anywhere in the product.
Air-gapped installation
RoadmapSelf-hosting assumes a connected host today. An offline install bundle, and reconnection sync for disconnected working, are recorded roadmap items.