Commercial Model

Pricing

Pricing is scoped around regulated deployment boundaries, workflow criticality, integrations, and assurance cadence so each engagement aligns to real delivery and risk obligations.

  • No public free tier. Designed for active governance programs.
  • Includes runtime policy, retention governance, API key posture, and boundary controls.
  • Scoped by environment count, workflow criticality, integration depth, and assurance cadence.
Request pricingBook demo

Private scoping call • Deployment-aligned pricing • No public free tier

Design Partner

Full implementation engagement (3-6 months)

Reduced-cost implementation in exchange for design-partner collaboration and roadmap feedback.

Fee credited toward year-one subscription upon annual conversion.

Core implementation

  • Full implementation across agreed boundaries and priority workflows

    By scoped implementation

  • Custom policy packs configured and applied

    Live today

  • Deterministic validators and enforcement for privacy, security, and compliance

    Live today

  • Baseline versus governed validation for key workflows

    Live today

  • Risk-at-rest identification and remediation priorities

    By scoped implementation

  • Escalation and audit workflows

    Live today

  • Governed override workflow in sandbox with explicit execution and audit telemetry

    Live today

  • Healthcare connector-boundary governance for FHIR/OAuth search and read flows

    Live today

Reporting and operations

  • Executive telemetry and reporting

    Live today

  • Support model

Enterprise scale and boundary operations

  • Multi-environment and multi-region deployment support

    By scope

  • Enterprise boundary connections for IAM, SIEM, and SOAR (for example, common platforms)

    By scope

  • Line-of-business segmentation and delegated controls

    By scope

Commercial structure

  • Design-partner collaboration cadence and roadmap feedback

  • Engagement fee credited toward year-one subscription on conversion

Implementation Program

12-week implementation program

Fixed-scope delivery program for teams moving from pilot controls into operational governance.

Core implementation

  • Full implementation across agreed boundaries and priority workflows

    By scoped implementation

  • Custom policy packs configured and applied

    Live today

  • Deterministic validators and enforcement for privacy, security, and compliance

    Live today

  • Baseline versus governed validation for key workflows

    Live today

  • Risk-at-rest identification and remediation priorities

    By scoped implementation

  • Escalation and audit workflows

    Live today

  • Governed override workflow in sandbox with explicit execution and audit telemetry

    Live today

  • Healthcare connector-boundary governance for FHIR/OAuth search and read flows

    Live today

Reporting and operations

  • Executive telemetry and reporting

    Live today

    Program telemetry pack

  • Support model

  • Priority support and contractual SLAs

Enterprise scale and boundary operations

  • Multi-environment and multi-region deployment support

    By scope

  • Enterprise boundary connections for IAM, SIEM, and SOAR (for example, common platforms)

    By scope

  • Line-of-business segmentation and delegated controls

    By scope

Strategic

Enterprise partnership

Enterprise-scale deployment, operational assurance, and deeper system-boundary coverage.

Core implementation

  • Full implementation across agreed boundaries and priority workflows

    By scoped implementation

  • Custom policy packs configured and applied

    Live today

  • Deterministic validators and enforcement for privacy, security, and compliance

    Live today

  • Baseline versus governed validation for key workflows

    Live today

  • Risk-at-rest identification and remediation priorities

    By scoped implementation

  • Escalation and audit workflows

    Live today

  • Governed override workflow in sandbox with explicit execution and audit telemetry

    Live today

  • Healthcare connector-boundary governance for FHIR/OAuth search and read flows

    Live today

Reporting and operations

  • Executive telemetry and reporting

    Live today

    Expanded telemetry pack

  • Support model

  • Priority support and contractual SLAs

Enterprise scale and boundary operations

  • Multi-environment and multi-region deployment support

    By scope

  • Enterprise boundary connections for IAM, SIEM, and SOAR (for example, common platforms)

    By scope

  • Line-of-business segmentation and delegated controls

    By scope

Commercial structure

  • Design-partner collaboration cadence and roadmap feedback

What it takes to implement LSAS Stack

We align on your boundaries and control objectives, then implement LSAS across the AI touchpoints and workflows you want governed.

PHASE 1

Align and define boundaries

  • • Boundaries and AI touchpoints in scope
  • • Control objectives and guardrails
  • • Success criteria and definition of done
PHASE 2

Implement and configure

  • • Gateway placement and wiring for your architecture
  • • Policy packs and workflow configurations
  • • Telemetry and reporting setup
PHASE 3

Validate and operationalize

  • • Baseline versus governed comparisons for key workflows
  • • Identify risk at rest and prioritize remediation
  • • Escalation, audit, and scale plan
Outputs: Policy packs • Workflow configurations • Executive telemetry • Audit-ready controls

You provide

  • • Executive sponsor (owns risk appetite and outcomes)
  • • Project representative (delivery lead)
  • • Domain SMEs for in-scope areas (for example, clinical or security)
  • • Inventory of systems, environments, and in-scope boundaries
  • • AI touchpoints and workflow map
  • • Control objectives and success criteria

We deliver

Architecture

  • • Boundary design and recommended gateway placement
  • • Implementation across agreed boundaries, including healthcare system-of-record edges, and priority workflows

Governance

  • • Custom policy packs aligned to your controls and risk tolerance
  • • Defined workflows for approvals and exceptions where needed

Validation and reporting

  • • Controlled baseline versus governed comparisons for agreed workflows
  • • Telemetry and executive reporting on risk posture and hotspots

Operationalization

  • • Identify risk at rest in in-scope systems and prioritize remediation
  • • Escalation and audit workflows, plus a scale plan to extend coverage

What you get in the first 90 days

This is the delivery cadence we operate against in active engagements, with explicit acceptance outputs and executive checkpoints.

Days 0-15

Scope lock and control alignment

  • • Signed boundary map for in-scope systems, environments, and AI touchpoints
  • • Control objective register with acceptance criteria and executive owners
  • • Implementation plan with risk-ranked workflow priorities

Days 16-45

Implement and prove controlled operation

  • • Runtime policy and onboarding controls configured for agreed workflows
  • • API key lifecycle controls active (create, revoke, role-gated access, audit trace)
  • • Baseline-versus-governed comparisons produced for priority use cases, including connector-boundary flows where in scope

Days 46-90

Production hardening and operating cadence

  • • Session lifecycle controls and key conflict telemetry reviewed with platform/security
  • • Audit event review workflow and escalation paths validated with operators
  • • Executive checkpoint package covering posture, gaps, and next-scope recommendations

Day-90 acceptance outputs

  • • Tenant-level control posture visible in console for runtime policy, retention, and API key governance.
  • • Evidence trail for high-risk actions in audit events with actor, action, and entity context.
  • • Runtime evidence and timeline visibility for governed connector-boundary executions in in-scope workflows.
  • • Version-safe key lifecycle operations that fail safely under concurrent admin actions.
  • • Agreed operating cadence for incident triage, exception handling, and roadmap expansion.

ROI measurement framework

We do not use inflated claims. We establish baseline operational metrics, measure deltas through rollout, and review value in executive cadence.

Value leverCommon baselineTarget state with LSAS
Governance review effortManual validation and ad hoc policy checks across teamsOperational reviews run from policy + audit telemetry with fewer manual handoffs
Time to detect control driftIssues found late in release cycles or during auditsDrift and conflict signals visible during normal operations
Audit preparation overheadEvidence collection spread across tickets, logs, and spreadsheetsDecision and mutation evidence pulled from centralized audit views
High-risk key and access hygieneInconsistent lifecycle and ownership practicesRole-gated lifecycle controls with explicit revoke, conflict handling, and traceability

Primary pricing drivers

  • • Number of production and non-production environments in scope
  • • Count and criticality of governed workflows and AI touchpoints
  • • Boundary implementation depth (IAM, SIEM/SOAR, internal platforms)
  • • Healthcare connector-boundary scope (FHIR/OAuth ingress and egress controls where required)
  • • Assurance model and operating cadence expectations