Frequently asked
The answer,without the fog.
Clear answers for buyers evaluating the platform, deployment model, extensibility, trust posture, and commercial structure.
Category 01
Platform & deployment
Is L2H a shared SaaS service?
L2H is customer-hosted. Your organization chooses the cloud or on-prem environment and the operating boundary for its deployment.
Can it run outside AWS?
Yes. L2H supports customer-selected cloud and on-prem deployment patterns. The right path depends on your infrastructure, identity, networking, and assurance requirements.
What about air-gapped environments?
The platform is designed to support air-gapped, classified, and high-assurance deployment patterns. Accreditation is held by the deploying customer or sponsoring agency.
How are upgrades handled?
L2H provides a controlled release and upgrade path for each deployment. Timing, validation, and change controls are aligned to the customer's operating process.
Where does customer content live?
In your own cloud account or data center. L2H is customer-hosted, so content stays inside the boundary you choose — your AWS, Azure, GovCloud, or on-prem Kubernetes — and L2H does not operate a multi-tenant service that holds your data. Retention, access, and integration specifics are confirmed during deployment planning.
Category 02
Model choice
Does L2H lock us into one LLM?
No. Model choice is configuration, not architecture. You connect the providers your organization approves and change that mix over time without rebuilding the experiences on top.
Can we change models without rebuilding workflows?
Yes. Model connections and per-role routing are configurable, so you can point a workflow at a different provider without re-authoring it. The exact change process depends on the deployment and the controls your organization applies.
Which model providers are supported?
Frontier and open-source models from OpenAI, Anthropic, Google, Meta, Mistral, Cohere, Amazon, and xAI, reached through OpenAI, Azure OpenAI, AWS Bedrock, or any OpenAI-compatible endpoint — including self-hosted runtimes such as vLLM and Ollama. We confirm the specific endpoints and operating pattern during solution design.
Category 03
Workflows & extensibility
Can other systems invoke L2H workflows?
Yes. Workflows can be made available to approved applications and agents through governed interfaces.
Do you support MCP and REST endpoints?
Yes. L2H can connect to MCP-compatible tools and REST endpoints selected by the customer.
Can L2H work with external agents?
Yes. The platform is designed for interoperable, governed agent workflows, including coordination with external systems where the deployment permits it.
How do you handle long-running or human-reviewed work?
Workflows can include long-running execution and human review patterns so automation can pause, gather a decision, and continue under control.
Can customers extend the platform?
Yes. The platform is modular and configurable so customers can add approved tools, endpoints, workflows, and user experiences without creating a separate AI stack.
Category 04
Security & compliance
What is the security posture?
L2H combines customer-hosted deployment, enterprise identity integration, auditable operations, and scoped access controls. The Trust Center states current architecture support, attestations, and roadmap status precisely.
What about IL5 and GovCloud?
L2H is in production at IL5 on customer-hosted GovCloud with private routing, and is architected for IL6+ deployment. Authorization to operate is held by the deploying customer or sponsoring agency.
Do you support classified and air-gapped environments?
L2H is designed to support deployment in air-gapped, classified, and high-assurance environments. Accreditation is held by the deploying customer or sponsoring agency.
Does L2H hold SOC 2, ISO, or FedRAMP attestations?
No. L2H does not currently hold SOC 2, ISO, or FedRAMP attestations. The architecture and controls are designed against relevant control families; see the Trust Center for the current posture.
How does authentication work?
L2H integrates with enterprise identity and access patterns. The specific configuration is selected to match the customer's environment and policy.
Category 05
Embedded Agents
Which host platforms are supported?
Embedded Agents are available for ServiceNow, VS Code, and — through the universal browser extension — any web application your teams use, including internal tools with no API. Deeper native implementations for other platforms can be scoped.
Why is Embedded Agents one product?
Each experience uses the same Agentic Command Center foundation for governance, model choice, and workflow access. The host experience changes; the command layer remains consistent.
Can the VS Code experience support coding teams?
Yes. Embedded Agents for VS Code brings organization-approved AI and workflows into the coding experience under the same customer-controlled foundation.
Category 06
ServiceNow
How do we control AI usage?
The experience includes configurable usage controls and reporting aligned to the customer's operating model.
How do we know it will work for our use cases?
L2H evaluates the experience against customer-selected content and workflows before production use. Success criteria are agreed for the evaluation.
Can it complement an existing Virtual Agent?
Yes. Embedded Agents can complement existing service experiences and escalation paths rather than requiring a wholesale replacement.
Does every configuration change require a redeployment?
Many operational behaviors are configurable. The deployment plan identifies which changes are managed by administrators and which require a controlled release.
What happens when an AI action fails?
The experience is designed for observable, auditable failure handling and clear escalation into the customer's support process.
Category 07
Pricing & contracts
How is pricing structured?
Agentic Command Center is the required foundation. Chat, Workflow Builder, and Embedded Agents are optional add-ons. Quotes are tailored to product scope, users, deployment boundary, support, and term; no public dollar rate card is published.
How do I buy?
Customers can buy directly from L2H, order on contract through our distributor Carahsoft, or use an applicable federal procurement path. Evaluation and multi-year structures are available.
Do you support federal procurement paths?
Yes. L2H is available through our distributor Carahsoft, including on NASA SEWP V, and works directly with agencies to align procurement to the command and contracting path. Use the contact form to discuss the current options.
Still deciding?