Enterprise questions, answered.

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.

Yes. Developer Evaluation is free and time-limited, with no credit card or model-provider account required. Verify your email and create a private evaluation workspace. Activate within seven days; the 14-day period starts with your first recorded governed decision. The allowance is up to 10,000 recorded decisions across your evaluation keys and routes, with 30 requests per minute and shared service limits. Blocked and held decisions count. Use synthetic or non-sensitive test data only, never production workloads or real credentials, personal or patient data. There is no perpetual production free tier. Discovery, pilots and production access follow a separate commercial process.

No. The API works with standard server-side HTTP clients. The downloadable evaluation harness and middleware exercise require Node.js 20+. Examples are available for cURL, Python, JavaScript, TypeScript, C#/.NET and Java, each with its own prerequisites. The native TypeScript example requires Node.js 24.12+. Copy an example, set your evaluation key locally and inspect the governed result in your private console.

Yes. Discovery Scan applies actual LSAS Platform policy checks to approved sources in a scoped, read-only assessment. You select policies in the local workspace, review executive findings and coverage gaps, and use the recommendations to shape a pilot. It demonstrates policy evaluation and reporting before live-workflow integration; it does not apply fixes to source data or establish comprehensive compliance.

LSAS Platform coordinates the scanner and approved local execution with you. Scanner distribution is restricted to LSAS Platform administrators; Developer Evaluation does not include scanner access. The offline scanner evaluates content locally and does not upload scan results to LSAS Platform. You control report sharing. File scans need no end-user runtime installation or configuration-file editing. Approved SQL Server connections require separate setup and qualification. Device approval, permitted sources, and any source-network connections are agreed during scoping.

Discovery: Contact for Pricing for up to 3 environments. Includes 4 hours of technical support per engagement. Expanded Discovery: Contact for Pricing for up to 6 environments. Includes 8 hours of technical support per engagement. Both cover one business and one agreed scope, with executive findings and coverage gaps, prioritized recommendations, proposed control points, an executive readout, and one follow-up scan of the same scope. Included support is separate from these implementation deliverables. Source types, workload limits, and final pricing are agreed before work begins. The pricing page sets out Evaluate → Discover → Pilot → Scale; the free Developer Evaluation uses synthetic or non-sensitive data and is separate from a paid Discovery assessment.

LSAS Platform is an AI governance evaluation platform with alignment workflows, structured assessments, policy validators, a model gateway, and connector boundary demonstrations. Supported text and payload paths produce decisions and findings. Enterprise hardening is under verification; production healthcare qualification has not been established. See the public enterprise-readiness page for current scope.

LSAS Platform combines decision records with controls on supported inputs and outputs. The gateway applies configured pattern validators and release rules. The sandbox also includes deliberately observed and simulated examples; those examples do not establish production enforcement.

A finding records the checks, policy context, and observations behind a decision. Structured assessments can check supplied evidence references and coverage. That trace does not prove source authenticity, factual truth, clinical correctness, or complete risk detection.

The current implementation does not independently verify arbitrary citations or factual claims against authoritative sources. Guided examples illustrate those risks, and the governed execution path withholds release when a required verification capability is unavailable. A pattern check or a supplied citation must not be presented as verified grounding.

LSAS Platform demonstrates boundary controls around an Epic sandbox integration using OAuth and FHIR. Its patient read and search presets make real requests to Epic's synthetic sandbox, alongside explicit simulation modes. This is a scoped integration demonstration, not an Epic certification or validated clinical workflow.

Storage depends on the subsystem. Gateway decision events contain derived telemetry, while connector payload snapshots, Run Engine assessment inputs and reports, and saved workflow definitions can contain raw supplied content. Configured external providers receive the content needed for their requests. Review the privacy page and retention configuration before supplying sensitive data; use synthetic data in the public sandbox.

LSAS Platform can be evaluated as part of a governance program. Suitability for a regulated production use has not been established. It requires verified controls, customer-specific identity and infrastructure evidence, intended-use assessment, and independent security and domain review. No certification or clinical validation is claimed.

Out of the box, LSAS Platform includes validators and policy controls for PHI and PII, PCI-like patterns, security and secrets exposure, prompt-injection patterns, and accessibility-related copy risks.

The adapter interface separates policy evaluation from supported model providers. Each provider, endpoint, model, and input format still needs explicit configuration and compatibility testing; provider independence does not imply universal API support.

Current runtime integrations cover OpenAI-compatible endpoints and Anthropic in this reference stack. Teams can extend provider adapters to support additional targets and enterprise routing patterns.

A native AWS Bedrock adapter is not included in the current reference implementation. The provider adapter interface offers an extension point, but Bedrock authentication, request mapping, transport controls, and integration tests would need implementation before claiming support.

The public sandbox is available for synthetic evaluation. Private single-tenant, customer cloud/VPC, and on-premises deployments are architecture options to qualify with the operator. The repository does not automatically provision their identity, network, residency, backup, or support controls. External provider access must be accounted for in each topology.

Teams can explore governance requirements and structured evidence handling using synthetic legal or advisory cases. Source authenticity and legal correctness are not established by the current validators. These demonstrations are not qualified for autonomous professional advice or release of client work product.

LSAS Platform models tenants, apps, memberships, and role-based access so teams can separate duties across security, compliance, and engineering while keeping a shared view of policy posture.

A proposed evaluation starts with intended use and data boundaries, followed by synthetic scenarios, control and failure testing, and deployment qualification. Milestones should depend on evidence and unresolved findings, rather than a promised 90-day production date.

The sandbox lets teams inspect example decisions and discuss their control requirements immediately. We do not have published customer outcome or time-to-production evidence. Deployment timing depends on the intended use and completion of its qualification gates.

Policy packs are versioned, assignable per tenant, app, and environment, and tied to decision telemetry. This supports change review and incident reconstruction with clear evidence of what policy version was active at decision time.

Evaluate reviewed policy packs against representative labeled examples, including missed detections and benign inputs, before changing assignments. Guided sandbox risk tiers compare fixtures; they do not edit an application's enforced policy. Pattern validators have limitations and require independent validation for the intended data.

The public sandbox includes a simulated override journey with explicit confirmation. Its recorded events are labeled public simulation activity, not authoritative tenant approvals, and it does not resume a real blocked action. The separate protected nonclinical review profile binds an assigned reviewer to an exact artifact and requires application consumption after approval. Its current grant lasts60seconds including generation; it is not a clinical sign-off workflow.

Start with a Discovery assessment with pricing agreed for your scope, progress to a fixed-scope 90-day pilot, and scale to annual platform pricing when ready. Pricing reflects the agreed source or workflow scope, environment footprint, and governance requirements. Discovery is available without a platform purchase. See the pricing page for both Discovery options, pilot structures, and annual platform offerings.

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. Full credit requires a qualifying 24-month commitment, a first-year annual subscription meeting the approved subscription minimum and at least equal to the qualifying pilot fee, approved production scope and conversion within 60 days of pilot acceptance. Applicable minimums are confirmed in signed commercial terms before the pilot begins. Smaller deployments may receive reduced credit with prior approval. Credits cannot create a negative balance, carry forward without written approval or credit the same payment twice. All credits and qualifying commitments must be documented before the pilot begins in the agreed contract, order form and statement of work.

Agree the deliverables, support ownership, intended use, and acceptance evidence explicitly. Available evaluation surfaces include onboarding, policy assignments, telemetry, and assessment reports. A package description does not establish a production SLA, certification, or validated healthcare deployment.

A production decision requires demonstrated authorization and isolation, suitable validation coverage, migration and recovery rehearsals, capacity evidence, incident ownership, and customer-specific security and domain review. A successful sandbox or passing local tests alone is insufficient. The current enterprise-readiness page lists the qualification limits.