Obsidian Core™
A local-first platform model for private workflow design — intended to run on your hardware, not as a hosted public cloud service.
Obsidian Core™ has limited public availability. Deployment is not open self-serve — requests are reviewed through a qualification process on a limited basis.
Platform Model
The Obsidian Core™ platform is designed around local-first operation: primary workflow activity stays on the user's local machine rather than depending on an always-on public cloud control plane.
Private workflow design means tasks, documents, and knowledge are organized for controlled use — structured for review, retrieval, and deliberate action rather than open-ended automation.
Approval-gated actions are part of the model: proposed steps can be reviewed before execution, so change stays intentional rather than automatic by default.
Deployment is controlled under S.V.E.N Inc.™ — scoped to qualified request and installation context, not mass public release or self-serve signup.
The following describe intended architecture and deployment-dependent capabilities — not guaranteed features on every install and not certifications or compliance claims.
- Local execution and local tooling where the deployment supports it
- Private document and knowledge organization for user-controlled material
- Approval-gated actions as a workflow design principle
- Document vault handling where configured for a given deployment
- Activity records that may be retained according to deployment scope and local policy
- Not a public cloud app
- Not a self-serve SaaS product
- Not an open public download
- Not an open-source release