Adoption evaluation
Select a reversible, non-production workflow; define success, exclusions, owners, and evidence before work begins.
Enterprise services
Adopt the MIT core. Contract for the work around it.
Phantom's CLI, local vault, proxy, and MCP server remain open source. Ashlr AI can discuss a written-scope evaluation, environment-specific integration, and support commitments. The agreement does not take away rights already granted by MIT.
Purchasable by written agreement
A precise engagement, built around your acceptance gate.
Integration engineering
Integrate the shipped local workflow with named repositories, operating systems, and supported AI clients.
Security review
Map Phantom's documented trust boundaries and known gaps to the controls your reviewers actually require.
How it starts
One bounded workflow. Evidence at every gate.
A successful source review is not a rollout. Each engagement separates proposal, implementation, verification, environment commissioning, and customer acceptance.
- 01Confirm that the shipped local-first boundary matches the problem.
- 02Write the scope, exclusions, deliverables, price, schedule, and acceptance tests.
- 03Implement and validate against an exact source and environment.
- 04Close with evidence, unresolved risks, and an explicit adoption decision.
Clear before procurement
Capabilities we do not sell as live today
- No generally available Phantom Cloud service or hosted control plane
- No shipped SSO, SAML, or SCIM integration
- No regulatory certification, authorization, or compliance attestation
- No contractual SLA unless one is expressly included in a signed agreement
- No supported self-hosted enterprise control plane
Requested product work can be scoped as proposed work. It is not represented as shipped, certified, commissioned, or accepted until separate evidence proves that state.