Enterprise Deployment
Your servers. Your network. Your keys.
We install the runtime inside your perimeter and leave. There is no outbound connection for your security team to monitor.
Straight Answers
- Outbound connections in normal operation
- Zero
- Telemetry or usage analytics collected
- None
- Data we can access on your deployment
- None
- Licence model
- Perpetual, no metering
- Runtime expiry
- Never
- Vendor lock on model weights
- None, open weights
Topology
Three perimeters. One engine.
The inference engine does not change. Only the boundary it sits inside does.
Perimeter · Your building
Runtime
Model weights
Your data
Inference happens here
Public internet
A server in your rack. Your IT team holds the keys.
- Inbound
- LAN only
- Outbound
- None after install
- Updates
- Manual, on your schedule
- Network
- Internal LAN
- Public endpoints
- None
- Model weights
- Local disk
- Air gap
- Supported
Sizing
What you will actually need to buy.
Set your seat count and workload. Take the result to your IT team before you talk to us.
Seats
Workload
60GB
VRAM
112GB
System RAM
20cores
CPU
612GB
Storage
- Nodes
- 1
- Peak concurrent sessions
- 6
- Model tier
- 8B to 14B class
- Profile
- Contracts and briefs read clause by clause.
- Outbound traffic
- 0 bytes
Indicative only. Assumes roughly one in eight seats querying at peak. We confirm the real spec against your workload on the assessment call.
Control Plane
IT manages it like any internal system.
Not a consumer app on staff laptops. A server runtime with a console.
Admin Console
One pane for health, usage and versions.
System health · Resource usage · Active sessions
Provisioning
Central grant and revoke, tied to your directory.
LDAP · Active Directory · SSO · Bulk assignment
Access Control
Matter walls that mirror your firm structure.
Practice group isolation · Permission tiers · Namespaces
Audit Logs
Every session, query and upload, tamper evident.
SIEM export · Configurable retention
Hardware
One departmental box up to a multi-node cluster.
x86 · ARM64 · CUDA · Multi-node
Updates
Applied when you approve them, never automatically.
Approval gates · Air-gap transfer · Rollback
For General Counsel
What we support, and what we have not earned yet.
We do not claim certifications we do not hold. The distinction is marked on every row.
Rule 1.6 requires reasonable efforts to prevent inadvertent disclosure of client information. External transmission is architecturally impossible here, so the disclosure surface does not exist.
Work product never transits a third party system. No external processor holds the material, so there is no waiver argument for opposing counsel and no vendor subpoena to defend.
Personal data stays in your jurisdiction. No cross-border transfer occurs, so Article 46 safeguards do not apply. You are both controller and processor.
Nothing is sold, shared, or disclosed to a third party because no personal information reaches our infrastructure. The obligations attach to data we hold, and we hold none of yours.
Not yet certified. Because our runtime processes nothing on our servers, the audit scope covers our development and distribution integrity rather than data handling.
Engagement
A structured engagement, not a sales cycle.
Four phases. You can stop after any of them.
We scope against your actual environment, not a generic demo.
- Infrastructure and hardware review
- Compliance and data residency constraints
- User count and workload profile
- Existing toolchain
Start with an assessment call.
Sixty minutes, no commitment. If we are not the right fit for your environment, we will say so on the call.