Pricing
Start free. Validate your requirements. Scale with confidence.
Choose the experience that fits your role. Both are free and independent.
No code required
Explore guided governance scenarios, inspect policy decisions, and understand enforcement outcomes without writing code.
A public demonstration environment. Start with synthetic guided scenarios; use synthetic or non-sensitive data only. This is not a private workspace.
For engineering teams
Test LSAS Platform using API keys and technical scenarios. Compare allowed, transformed, blocked and held results; inspect and export detailed governance evidence from your private workspace.
Free, time-limited access with synthetic or non-sensitive test data. No credit card or model-provider account required. No production use.
See code examplesDeveloper Evaluation allowance: 14 days from the first recorded governed decision · Up to 10,000 recorded decisions · 30 requests/minute.
Activate within seven days of workspace creation. Blocked and held decisions also count. The allowance is shared across your evaluation keys and routes, subject to service limits. Evaluation results do not establish production readiness or comprehensive detection.
No perpetual production free tier. Production access is scoped through a commercial agreement.
Choose the engagement that fits your scope. These are independent starting points, not mandatory prerequisites. Pricing tailored to your scope, with fees agreed before work begins.
See LSAS Platform work on your data before you commit to a pilot.
Discovery engagement
Contact for Pricing
Up to 3 environments · One business. One agreed assessment scope.
A focused first assessment to identify findings and shape your pilot.
Includes 4 hours of technical support per engagement.
Request PricingDiscovery engagement
Contact for Pricing
Up to 6 environments · One business. One agreed assessment scope.
The same evidence and guidance across a wider set of environments.
Includes 8 hours of technical support per engagement.
Request PricingPricing is confirmed for the agreed scope before work begins. Environments are approved source contexts, not unlimited data volume. Source types, access, workload limits, and timing are agreed during scoping. File scans are ready to use; SQL Server connections require separate setup and qualification.
More than six environments, multiple businesses, or substantially larger data volumes are scoped separately.
The offline scanner evaluates content locally and does not upload scan results to LSAS Platform. You control report sharing.
Discovery evaluates selected policies without changing source content. Findings inform review and proposed control points; the pilot then tests runtime controls in an agreed workflow. No platform purchase is required for Discovery.
Eligible Discovery fees may be credited toward a subsequent paid pilot according to the agreed statement of work. A Discovery credit reduces the incremental pilot payment. It does not create a separate credit against the platform subscription. See conversion terms.
Every pilot runs the same operating cadence and ends with a day-90 acceptance package. The fee is fixed after scope and the statement of work are agreed.
90-day pilot
Contact for Pricing
Fee fixed after scope agreement
For a single team proving governance on live workflows.
Includes 10 hours of technical support over the 90-day pilot.
Request Pricing90-day pilot
Contact for Pricing
Fee fixed after scope agreement
For multi-team rollouts with integration requirements.
Includes 20 hours of technical support over the 90-day pilot.
Request Pricing90-day pilot
Contact for Pricing
Fee fixed after scope agreement
For regulated environments and connector-heavy architectures.
Includes 40 hours of technical support over the 90-day pilot.
Request PricingIncluded support is separate from the implementation, validation and acceptance deliverables purchased through Discovery or a pilot. The support allowance covers eligible technical assistance outside those planned deliverables; it is not the total implementation effort.
See the 90-day operating cadenceQualifying pilots may receive up to 100% credit toward the first-year platform subscription, subject to conversion and commitment terms.
See conversion termsChoose the deployment architecture that fits your organization. Production access requires a commercial agreement; no evaluation or pilot is a mandatory prerequisite.
Platform subscription
Contact for Pricing
Subscription scoped to your deployment
For teams running governed AI workloads on shared infrastructure.
Includes 2 hours of Standard support per month.
Request PricingPlatform subscription
Contact for Pricing
Subscription scoped to your deployment
Inline proxy for organizations that need enforcement at the boundary.
Includes 6 hours of Priority support per month.
Request PricingPlatform subscription
Contact for Pricing
Custom deployment pricing
For regulated environments that require private deployment.
Dedicated support starting at 8 hours per month; actual allowance scoped in the executed order form.
Request PricingPilot tiers represent evaluation scope, complexity and acceptance requirements. Platform offerings represent deployment architecture and ongoing operating requirements. A Business Unit or Enterprise pilot does not automatically require Gateway. Each deployment is priced for its approved scope.
Private deployment, identity and external integrations are scoped delivery work, with acceptance criteria and operating responsibilities agreed in your statement of work.
Customers provide the agreed infrastructure and storage environment. LSAS Platform supplies the supported application; deployment-package scope and delivery are defined in the statement of work. Deployment, patch management, backup, recovery and support responsibilities are defined in the applicable agreement.
Customer-operated PostgreSQL, networking, storage and infrastructure backups remain customer responsibilities unless separately contracted. Configured providers or connectors may transmit permitted payloads beyond the deployment boundary; architecture and network requirements are reviewed for each deployment.
Explore Private Deployment & Shared ResponsibilityCommercial details
Understand credits, support allowances and scope before you commit. Essential conditions remain part of your agreed commercial terms.
A successful pilot should make the next decision easier, not require you to start over. When you convert to a qualifying LSAS Platform agreement within 60 days of pilot acceptance, up to 100% of your qualifying pilot fee may be credited toward your first-year platform subscription.
The applicable full-credit subscription minimum is confirmed in the approved quote before the pilot begins; it is a qualification condition, not a new platform tier.
A smaller platform deployment may qualify for a reduced conversion credit, subject to approval and terms established before the pilot begins.
Conversion credits apply only to eligible first-year platform subscription fees; they are not cash refunds and cannot create a negative subscription balance.
Credits cannot carry forward to future contract years unless explicitly approved in writing, and the same underlying customer payment cannot be credited twice.
The qualifying pilot fee retains its existing conversion-credit treatment, including the support embedded in that fee. Separately billed support overages and professional services are not automatically eligible for pilot-conversion credits.
All credits and qualifying commercial commitments must be documented before the pilot begins and are subject to the agreed contract, order form and statement of work.
An eligible Discovery payment may reduce the incremental payment for a subsequent pilot. The qualifying pilot investment includes that credited payment once; Discovery does not create a second, independent platform credit.
With approved production scope, the applicable subscription minimum and a qualifying 24-month agreement signed within 60 days of pilot acceptance, up to 100% of the qualifying pilot fee may be credited toward the first-year subscription. The second year remains payable under the agreement. This is a subscription credit, not a cash payment or refund.
Every paid LSAS Platform engagement includes a defined level of technical assistance aligned to its scope, complexity, and deployment requirements.
For Cloud API and limited-scope implementations.
For Gateway and higher-complexity implementations. Includes everything in Standard, plus:
For private deployments and larger enterprise environments. Includes everything in Priority, plus:
Included support is separate from the implementation, validation and acceptance deliverables purchased through Discovery or a pilot. The support allowance covers eligible technical assistance outside those planned deliverables; it is not the total implementation effort.
Additional standard technical support and specialized architecture, advanced integration or engineering services are separately quoted. Scope, rates or a fixed fee must be agreed and authorized before work begins.
Support hours are separate from coverage windows, initial incident acknowledgment, severity and escalation, restoration and resolution efforts, and platform availability. Applicable SLA commitments are documented in the executed service agreement. Initial acknowledgment is not guaranteed resolution; no 24/7 coverage or uptime target is included by default.
Discovery allowances expire at the conclusion of the engagement; pilot allowances expire at the conclusion of the 90-day pilot.
Monthly subscription allowances do not roll over by default. Hours cannot transfer between contracts unless agreed in writing.
Additional billable support requires customer authorization before work begins. Expanded implementation scope requires a change order.
Custom policy development, new integrations, substantial architecture changes and professional services are separately scoped; they do not automatically consume ordinary support allowances.
Serious product incidents can still be reported after included hours are exhausted. Incident handling and any charges are governed by the applicable support agreement.
Support allowances are service hours, not refundable balances or subscription conversion credits. Categories do not provide unlimited engineering access or an embedded engineer.
Eligible assistance includes technical troubleshooting, configuration, supported API guidance, product issue investigation, documentation and release guidance, standard policy configuration, and access to approved updates. Cloud API includes Standard, Gateway includes Priority, and Self-hosted / VPC includes Dedicated support. Discovery and pilot allowances cover assistance for the agreed engagement; they do not automatically assign an annual support category. Custom policy development and new integrations are separately scoped services.
Included support is separate from the implementation, validation and acceptance deliverables purchased through Discovery or a pilot. The support allowance covers eligible technical assistance outside those planned deliverables; it is not the total implementation effort.
Additional billable assistance requires customer authorization before work begins. Scope and pricing for additional technical support are agreed in a separate quote. Serious product incidents can still be reported; incident handling and any charges follow the applicable support agreement. Expanded implementation scope requires a change order.
Discovery allowances expire at the conclusion of the engagement; pilot allowances expire at the conclusion of the 90-day pilot. Monthly subscription allowances do not roll over by default. Hours cannot transfer between contracts unless agreed in writing. Allowances are service hours, not refundable balances or subscription conversion credits.
Additional standard technical support and specialized architecture, advanced integration or engineering services are separately quoted. Scope, rates or a fixed fee must be agreed and authorized before work begins. Additional billable work requires customer authorization before it begins. Custom policy development, new integrations and substantial architecture changes are separately scoped, not automatically charged against ordinary support hours.
LSAS Platform supplies supported software releases and product patches. Scheduling, testing and applying updates within customer-operated environments are shared responsibilities defined in the statement of work and service agreement, including customer IT coordination, access, change windows and recovery procedures.
For private deployments, the customer provides and operates the agreed PostgreSQL and storage environment, including infrastructure backups and disaster recovery, unless separately contracted. The customer owns retention settings and regulatory retention decisions. Backup restoration and recovery responsibilities must be qualified for the actual deployment.
Coverage and availability requirements are reviewed during scoping and must be validated operationally and documented in the executed service agreement. Included hours do not imply 24/7 coverage, an uptime percentage, or response or restoration guarantees. Initial acknowledgment is separate from resolution.
Yes, support scope, coverage and coordination can be agreed to fit the deployment. Dedicated support starting at 8 hours per month; actual allowance scoped in the executed order form. Dedicated support provides a named technical contact, not unlimited engineering access or an embedded engineer unless expressly contracted.
The qualifying pilot fee retains its existing conversion-credit treatment, including the support embedded in that fee. Separately billed support overages and professional services are not automatically eligible for pilot-conversion credits. Existing qualification requirements remain: a qualifying 24-month commitment, conversion within 60 days of pilot acceptance, the applicable first-year subscription minimum and approved production scope. The same underlying payment cannot be credited twice; credits are not cash refunds and do not roll over without written approval.
Scope and delivery
Final pricing is set on a scoping call around four drivers — the platform tiers above are starting points, not ceilings. Pilot prices are fixed for the agreed scope.
The delivery cadence pairs explicit acceptance outputs with executive checkpoints.
Days 0-15
Days 16-45
Days 46-90
We establish baseline operational metrics, measure deltas through rollout, and review value in executive cadence.
Define your workflows, deployment boundaries, and day-90 acceptance criteria.
An open invitation
The challenges organizations face with AI aren’t theoretical. We’re learning from the people navigating them every day.
If you work in governance, risk, compliance, enterprise architecture, security, or AI engineering, we’d welcome your perspective.
A conversation, not a sales pitch.
