Deploy Phalanx
Start with one workflow worth putting under control.
Bring the agent, the business systems it can reach, and the actions you need to govern. We will define a focused evaluation around your task authority, protected routes, and success criteria.
Current demo: Meridian baseline, before Phalanx enforcement.
Make the first boundary concrete.
A good starting point has a clear task, a small set of consequential actions, and a technical owner who can change the integration. Together, we identify the credentials, state checks, approvals, and results that define the boundary.
The work
What should the agent accomplish, and which actions must it take?
The authority
Which resources, destinations, limits, and approvals apply to that task?
The route
Where do the real credentials live, and which alternative execution paths must be closed?
The result
How will the connected systems show that an action succeeded, failed, or remains uncertain?
From a proposed workflow to an evaluated deployment.
- 1. Review the fitDescribe the workflow, model route, business tools, and deployment environment. We confirm what can be supported and what integration work is needed.
- 2. Agree the evaluationDefine the protected actions, acceptance criteria, responsibilities, licensing, support, and commercial terms before deployment work begins.
- 3. Connect the boundaryIntegrate the agent through the supported interface, configure task authority, place credentials behind protected connectors, and verify route coverage.
- 4. Exercise the workflowTest useful authorized actions, scope violations, holds, changing state, repeat operations, and dependency failures in the agreed environment.
- 5. Review the evidenceExamine the outcomes and remaining limitations, then decide the next deployment step.
Customer-controlled execution with a supported delivery path.
Phalanx is licensed software deployed within the customer boundary. Customer delivery uses signed releases and a dedicated command-line workflow. The scope of the supported runtime, connectors, operational checks, and upgrade procedure is confirmed for the evaluation.
The core authorization path runs locally. Your configured external models, evidence sources, and business services remain part of the deployment's data-flow and security review.
Commercial terms are agreed for the scoped engagement. Submitting an inquiry does not purchase a license or start an evaluation.
A strong fit starts with control of the integration.
You can define structured task authority, isolate the credentials for the protected actions, and verify the relevant system state. You also have a technical owner who can enroll the tool routes and test the result.
If the agent must retain an equivalent credentialed route around Phalanx, that action cannot carry the gateway's protection claim. We will identify that during the fit review.
Tell us what your agent needs to do.
A short description is enough to start. Focus on the workflow, the systems involved, and the action you want to control.