Deployment
What deployment includes
Deployment is a configured installation on client-controlled hardware, with a managed private Vault on the deployment drive and the Obsidian Core application for day-to-day use.
Operational status
Deployment requests are currently accepted on a limited basis. Each install is built around that business—pricing rules are not hardcoded to any one company.
Process
How an install is set up
Typical steps for a qualified deployment. Order and detail can vary by business, but the goal is the same: a working back office configured to how you operate.
-
Business workflow review Map how jobs start, what documents you issue, and how payments and closeout work today.
-
Company and pricing-profile configuration Capture services, rates, minimums, deposits, markups, fees, taxes, terms, exclusions, and change-order rules for that business.
-
Job-sequence and document-template setup Configure repeatable job sequences and the document templates your office actually uses.
-
Vault and storage preparation Prepare the managed private Vault on the deployment drive for structured business records.
-
Local application installation Install the Obsidian Core application on the client-controlled hardware for that deployment.
-
Approval and governance configuration Set which consequential actions require owner approval and how status and history are recorded.
-
Operator onboarding Walk through creating a job, filing uploads, drafting documents, approving actions, and recording payments.
-
Validation and handoff Confirm the configured workflows, then hand off with guidance for ongoing use.
Expectations
What deployment does not promise
- Not open public availability or instant self-serve download
- Not remote management of your entire business by default
- Not automatic legal or tax compliance for every jurisdiction
- Not unlimited third-party integrations without scoped configuration