Three founding deployment slots
Integrate Phalanx at one consequential instruction boundary.
The current commercial offer is a tightly scoped, founder-supported pilot for an English written-text LLM application that can preserve typed provenance and enforce protected output or action boundaries.
Good first fit
A bounded application with an owner who can change the integration.
The first deployment should prove security and operational fit without pretending Phalanx is a drop-in answer for every LLM architecture.
Application
- Chat or document/RAG assistant
- Support copilot
- Bounded tool-using workflow
- English written-text input
Integration
- Backend assigns provenance
- Session state is server-owned
- Consequential sinks can be wrapped
- Technical owner available for a 20-minute call
Not this pilot
- Multimodal or layout-dependent PDF understanding
- General moderation or factuality
- Flattened untyped content
- Unrestricted real tools or infrastructure defense
Pilot process
From application boundary to deployment decision.
- 01QualifyConfirm the application has an English written-text boundary, a technical owner, and a host-controlled integration point.
- 02ScopeDefine trusted and untrusted channels, protected outputs/actions, expected latency, failure behavior, and deployment topology.
- 03IntegrateRun Phalanx in-process or behind a private HTTP boundary and wrap consequential sinks with one-use permit enforcement.
- 04ValidateExercise direct, indirect, mixed, benign, dependency-failure, release-identity, and rollback gates in the customer environment.
- 05DecideDeliver a bounded pilot result, known limitations, and the next deployment decision without implying an SLA or universal guarantee.
Available delivery
Customer-hosted and release-bound.
The accepted package supports in-process Python and private HTTP delivery in the qualified one-process topology. The product includes signed release identity, health/readiness checks, redacted audit evidence, and verified rollback.
Commercial boundary
No public price, hosted commercial API, formal SLA, standalone executable, or universal deployment profile is offered here. Fit, topology, support, licensing, and acceptance gates are scoped before a pilot begins.
Qualification