Pilot and License Access
License a sealed judgment perimeter for your firm — not software seats, not another drafting tool.
At A Glance
Vendor Hosted
SEAL Legal Runtime is licensed as
vendor-hosted governance infrastructure — no on-prem install, no admin console to manage.
Auditability
You don’t buy users or features. You license the right to route governed filings and high-risk actions through a sealed API that enforces your policies and produces audit-ready artifacts.
Visibility
Internals stay sealed. You see approvals, refusals, overrides, and their artifacts — not rule logic or model traces.
We are accountable for the correct functioning of the sealed runtime as a control.
You are accountable for your policies, identity, and how you practice law.
How the SEAL License Works
Per legal tenant, not per user
– One license per law firm or distinct corporate legal department.
– Unlimited reviewers and filings within fair-use and operational limits.
Vendor-hosted, sealed API
– No on-prem install, no admin console, no prompt interface.
– Your systems call SEAL; SEAL returns an approval or refusal, plus a sealed audit artifact.
Legal-only scope (today)
– Licensed for use in agreed legal domains (e.g., criminal defense, civil litigation, securities).
– Non-legal use (HR, marketing, etc.) requires a separate agreement.
Who the License Is For
For Law Firms
- Use SEAL as a gate on motions and filings that could reach a court or regulator.
- Partners keep control; SEAL provides the sealed record of what was allowed or refused.
For Corporate Legal Departments
- Govern in-house filings, approvals, and high-risk actions (e.g., disclosures, regulatory submissions).
- Aligns with existing GRC and IdM; SEAL never replaces your policies or systems of record.
For Legal Tech Vendors
- By separate OEM license, embed SEAL as an invisible enforcement layer behind your platform.
- Your UI stays yours; SEAL quietly refuses what should never run.
Evaluation, Pilots, and Command-Layer License
Governed Runtime Exposure (Pre-License)
- Short, vendor-hosted exposure with no connection to your systems.
- Used for ethics committees, risk, and outside counsel to see how sealed approvals/refusals behave.
- Every run still produces a sealed artifact; no internal logic is exposed.
Sealed / Integrated Pilot
- Time-boxed pilot where SEAL is wired into your SSO, matter system, and routing.
- Your roles, policies, and terminology start driving decisions.
- Governed by a
Pilot Charter (scope, roles, rollback conditions).
Command-Layer License (Production)
- Enduring commercial license for a named legal tenant.
- Covers all licensed legal domains; no seat-based fees.
- SEAL becomes a mandatory gate for chosen workflows, with sealed artifacts used for malpractice defense and audit.
Responsibility and Risk: Who Owns What
You (the Firm / Legal Tenant):
- Own your GRC and ethics policies (what is allowed, advisory, or blocked).
- Own identity and access control (who is a partner, associate, paralegal, agent).
- Decide which workflows must pass through SEAL and who sees what internally.
- Remain responsible for supervising lawyers, staff, and tools.
Thinking OS™:
- Owns the sealed enforcement runtime and its operation.
- Ensures that every governed request either:
– passes configured checks and receives a sealed approval
– fails closed with a sealed refusal and clear code. - Maintains security, integrity, and availability of the runtime within agreed SLAs.
- Provides artifacts and logs designed to support your malpractice and regulatory posture.
Bottom Line
“We are accountable for the correct functioning of the sealed runtime as a control.
You are accountable for your policies, identity, and how you practice law.”
What You Get Under the SEAL License
- A dedicated tenant profile
– Your identity posture (SSO / IdP), routing endpoints, and legal scope.
– Configured once, then enforced consistently at runtime.
- Rights to use SEAL in live matters
– Route real filings and governed actions through a sealed API.
– Treat SEAL’s approval/refusal artifacts as part of your matter and audit record.
- Coverage across all shipped legal domains (for that tenant)
– No per-vertical surcharge, no per-motion pricing.
- Sealed, audit-ready artifacts for every decision
– Approvals, refusals, and overrides come with a stable code, rationale, and traceable metadata.
– Designed for malpractice defense, bar inquiries, and regulatory review.
What the License Does Not Grant (By Design)
- No access to internal logic or models
– No prompts, weights, decision trees, or rule code.
– No right to reverse-engineer, clone, or emulate the runtime. - No right to host SEAL internals
– SEAL operates as a vendor-hosted, sealed API; we do not ship it on-prem. - No general-purpose AI governance rights
– The legal runtime license does not grant rights to govern arbitrary non-legal workflows.
– Other domains (e.g., finance, health) would require separate runtimes and agreements. - No guarantee of ethical compliance
– SEAL is a governance control; it is not a substitute for professional judgment or supervision.
– Your firm remains responsible for how you practice law and how you use SEAL.
Security and Compliance Fit
- Vendor-hosted in an enterprise-grade cloud environment.
- Designed to support alignment with SOC 2, ISO 27001, and legal ethics obligations (e.g., supervisory duties, confidentiality, unauthorized practice).
- SEAL
never becomes your GRC system; it enforces the posture you configure and produces artifacts you can map into your own frameworks.
How to Move Forward
For GCs, MPs, and practice leaders, the path always starts the same: a confidential briefing under NDA.
- Confidential Briefing (Under NDA)
– Deep dive with GC, risk, and practice leadership on enforcement model and artifacts. - Pilot Governance Charter
– Agree on scope (vertical, motions, courts), roles, and safeguards for a sealed pilot. - Pilot Integration Checklist
– Your IT / IdM / KM teams complete a short checklist so SEAL can be wired in cleanly. - Command-Layer License & Order Form
– Once pilots are successful, we execute a tenant-level license and activate production use.
Licensing FAQ
“Does SEAL replace our DMS, case system, or drafting tools?”
No. SEAL sits in front of them as an enforcement layer. It never drafts or files.
"Will SEAL make decisions for our lawyers?"
No. SEAL is a governance control. It enforces your configured rules and records what was allowed or refused. Attorneys remain fully responsible for filings, advice, and strategy.
“Is this priced per user or per case?”
No. Licensing is per legal tenant, covering all licensed verticals, with unlimited reviewers and filings within operational limits.
“Where does data live?”
SEAL operates as a vendor-hosted API and writes sealed artifacts into client-owned storage or agreed locations; it does not become your system of record.
“Can we inspect your rule logic?”
No. The runtime is sealed by design. What you see are stable codes, rationales, and artifacts that support audit and oversight.Describe the item or answer the question so that site visitors who are interested get more information. You can emphasize this text with bullets, italics or bold, and add links.