PLATFORMS
Build it on LangGraph, Bedrock, Vertex or Azure. Make it earn production on Scalarion.
The platforms that build and run agents are where your agents live. Scalarion is the release decision above them: it reads what the agent is, records who decided it may ship and on what conditions, and checks that decision where the deployment happens.
What Scalarion adds to any of them
An accountable human decision bound to the exact agent digest, sealed as evidence a third party can verify without trusting Scalarion, and checked where the deployment happens.
THREE POINTS EVERY STACK HAS
Intake — What exactly is the agent? · Gate — Where does it go live, and is it allowed to? · Signal — What did it do once it was there?
LangGraph / LangChain
- IntakeIn build
- A dependency-free exporter reads the compiled graph — its tools and the models its nodes reach — and the intake turns it into a release manifest. Permissions and model versions are declared; provider wire ids are refused unless a canonical name is declared.
- GateIn build
- The admission CLI runs as a step before the deploy and fails it when no current authorization matches the digest.
- SignalRoadmap
- LangSmith traces and evaluations attached to the digest as evidence.
AWS Bedrock / AgentCore
- IntakeRoadmap
- Agent configuration, action groups and guardrails normalised into a manifest, with the canonical model name and Bedrock kept as the provider.
- GateIn build
- The admission CLI runs as a step before the deploy and fails it when no current authorization matches the digest.
- SignalRoadmap
- AgentCore and CloudWatch observability as a drift signal.
Azure AI Foundry
- IntakeRoadmap
- Agent definition, model deployment and tools normalised into a manifest.
- GateIn build
- The admission CLI runs as a step before the deploy and fails it when no current authorization matches the digest.
- SignalRoadmap
- Foundry evaluations and tracing as evidence and drift signal.
Google Vertex AI
- IntakeRoadmap
- Agent and tool specification normalised into a manifest.
- GateIn build
- The admission CLI runs as a step before the deploy and fails it when no current authorization matches the digest.
- SignalRoadmap
- Vertex evaluation and tracing as evidence and drift signal.
Custom / any stack
- IntakeIn build
- A release manifest written by the team and digested by the same canonicaliser every intake uses.
- GateIn build
- The admission CLI runs as a step before the deploy and fails it when no current authorization matches the digest.
- SignalRoadmap
- OpenTelemetry.
THE CONTRACT WITH EVERY PLATFORM
- Scalarion never runs your agent in production. The runtime here exists to seal what runs, not to host it.
- Scalarion never holds your model keys. Intake reads a document your pipeline writes; nothing reaches into your stack.
- Your provider is part of your digest. Moving an agent from one provider to another is a new subject, and a new decision.
- Scalarion's own inference provider is never written into your manifest. How we run our drafter cannot move your digest.