Everything you need to partner with Resurrection Tech™.
One link, one source of truth. After a discovery call, this is where partners find what Runtime Governance is, how the partnership works, the commercial and integration options, the executive-reporting layer, and the answers to the questions that usually take three more meetings.
Executive summary
What it is. Runtime Governance evaluates an agent’s proposed actions before they execute and returns ALLOW, BLOCK, or ESCALATE — keeping reachable trajectories out of forbidden states (Ω).
Why enterprises need it. Autonomous agents now touch payment systems, customer data, infrastructure, and regulated workflows. Pre-execution control is becoming a deployment requirement, not a feature.
Why partners make sense. You already hold the customer relationship, the security mandate, or the platform. Partners extend existing services into governed AI without inventing reachability-based governance themselves.
Expected customer outcomes. Safe agent deployment, board-ready evidence, faster compliance, and prevented incidents — with the partner owning the relationship and the renewal.
Choose the motion that fits your business.
From introductions to embedded licensing — every model, with who it’s for and how it works.
Strategic Alliance Partner™
Referral Partner
Managed Governance Partner™
OEM Partner
Embedded Licensing™
Enterprise Licensing™
Technology Partner
Channel Partner / Reseller
Who provides what.
Across Resurrection Tech, the partner, and the end customer.
| Responsibility | Resurrection Tech | Partner | End customer |
|---|---|---|---|
| Sales | Enablement | Lead | — |
| Technical onboarding | Lead | Support | — |
| Runtime Governance API | Owns | Integrates | Consumes |
| Integration | Guides | Lead | Participates |
| Support | Escalation | First-line | Raises |
| Executive reports | Generates | Presents | Receives |
| Renewals | Supports | Lead | Decides |
| Customer success | Enables | Lead | — |
| Security updates | Owns | Applies / informs | — |
| Training | Provides | Delivers | Consumes |
| Compliance | Governance evidence | Maps to frameworks | Owns posture |
| Governance updates (Ω) | Owns | Reviews | — |
| Incident response | Engine / root cause | Customer-facing | Reports |
How engagements are structured.
A ladder of engagements, not a price list. Each is scoped to where the partner and customer are.
Partner Discovery Workshop™
Structured scoping of a prospective partnership — fit, customers, and go-to-market. Credited toward onboarding.
Managed Governance Partner™ Onboarding
Strategic enablement that prepares you to sell and deliver governed AI before introducing it to customers.
Limited Pilot™
Validate Runtime Governance against real workflows in a bounded, observable engagement.
Runtime Governance Audit
Identify catastrophic trajectory exposure and governance gaps in a fixed, fast engagement.
Enterprise Integration
One-time production deployment into operational systems.
Annual Runtime Governance Licence™
Ongoing governance — monitoring, updates, support, and revalidation.
Executive Reporting
Monthly board-ready evidence, included with engagements (not a separate purchase).
Board Reporting
Executive summaries packaged for leadership and governance committees.
OEM / Enterprise Licensing™
Embedded, white-label, sovereign, or large-scale licensing by commercial review.
How pricing works.
When fixed pricing applies. Standard-ladder engagements have indicative bands — Runtime Governance Audit (£40K–£75K), Limited Pilot (£250K–£750K+), Annual Licence (£75K–£500K+/yr), Advisory Retainer (£35K–£100K+/mo), and Managed Governance Partner onboarding (£25K–£50K, recommended £35K).
When commercial review applies. Enterprise Integration, embedded/OEM/enterprise licensing, white-label, exclusivity, territory, and large-scale or sovereign deployments are scoped commercially.
When annual commitments apply. Ongoing platform access, licensing, and embedded models carry a minimum annual commitment confirmed during review.
Onboarding vs implementation. Onboarding is strategic enablement — it prepares a partner to sell and deliver governed AI. It is not a discount on enterprise pricing, and customer engagements continue through the standard ladder unchanged. Implementation is the technical work to deploy for a specific customer.
See the full ladder on the Enterprise pathways & pricing page.
Model the value of prevention.
One prevented catastrophic action can outweigh a year of governance. Adjust the inputs to your customer’s situation.
On these assumptions, preventing 2 catastrophic incidents a year worth £2,000,000 each against a £250,000 investment returns £3,750,000 in net annual value — a 16.0× return.
Generate Executive ROI ReportIllustrative model, not a guarantee of savings. Incident costs reference documented industry precedents; actual exposure and prevention depend on your environment, agents, and governance configuration. Investment bands map to Resurrection Tech engagements (audit, pilot, annual licence, managed platform).
Format-agnostic by design.
Runtime Governance makes a format-agnostic decision. The decision logic does not change per API — so for most stacks, integration is an adapter problem, not a rebuild. Anything that can make an HTTPS POST can connect.
Frameworks and agent stacks pass proposed actions through a thin adapter that normalises them to a single contract; the engine evaluates each one and returns ALLOW, BLOCK, or ESCALATE before execution.
Four ways to connect.
Hosted API
Fastest deployment — call the governance API over HTTPS.
Customer cloud
Run it in your own AWS, Azure, GCP, or private cloud.
Embedded SDK
Integrate the governance layer directly in your runtime.
Network proxy / sidecar
Govern actions transparently, with no agent code changes.
Integration effort varies. It depends on how cleanly a framework exposes tool-execution hooks, its authentication model, whether it streams or uses request/response, and the customer’s deployment constraints. Stacks already close to our contract integrate quickly; others take longer. We scope each integration as an engineering estimate, not a fixed timeline.
Deploy where your organisation needs it.
Runtime Governance is deployment-model agnostic. Organisations can deploy the governance layer in the environment that best fits their security, compliance, operational, and data residency requirements.
Hosted by Resurrection Tech
- Fully managed Runtime Governance API
- Fastest deployment
- Continuous updates
- Monitoring and support
- Ideal for organisations that want minimal operational overhead
Customer Cloud Deployment
Host Runtime Governance within your own approved cloud environment:
- AWS
- Microsoft Azure
- Google Cloud Platform (GCP)
- Private cloud
- On-premises infrastructure (where appropriate)
Resurrection Tech deploys, configures, validates, and supports the governance layer while you retain control of your own infrastructure if desired.
Dedicated Enterprise Deployment
For highly regulated environments:
- Private networking
- Customer-controlled infrastructure
- Compliance-driven deployment
- Dedicated environments
- Enterprise support
- Custom integration architecture
Deployment location is determined during technical discovery and implementation. Runtime Governance can be delivered as a managed API, customer-hosted deployment, or licensed enterprise deployment depending on operational, regulatory, security, and commercial requirements. The deployment model changes where Runtime Governance runs — not who owns it: Resurrection Tech retains ownership of the governance engine, intellectual property, updates, and licensing rights regardless of deployment location. Compare integration models →
Runtime Governance Executive Reports™
The API protects the system. The report proves the value.
Runtime Governance Executive Reports™ turn runtime activity into board-ready evidence. Each report shows what was protected, what was prevented, what changed, and what actions are recommended next — so Runtime Governance does not only block unsafe actions, it demonstrates its value.
What was protected
The systems, data, and tools your agents could reach.
What was prevented
Unsafe actions blocked before they executed.
What changed
New tools, risks, or trajectories since the last period.
Governance posture
Current coverage against forbidden states (Ω).
ALLOW / BLOCK / ESCALATE metrics
Verdict volumes and trends over time.
Audit trail status
Tamper-evident record of every decision.
Risk reduction actions
Steps taken, and those still outstanding.
Executive recommendations
Prioritised next actions for leadership.
A recurring record customers can act on.
Delivered monthly, the reports give partners and customers evidence to support:
What a report contains.
- Executive SummaryThe period at a glance for leadership.
- Runtime ActivityVolume and pattern of governed actions.
- Actions PreventedUnsafe trajectories blocked before execution.
- EscalationsWhat was routed for human review, and outcomes.
- Governance PostureCoverage against forbidden states (Ω).
- Risk ReductionMeasured change in reachable exposure.
- RecommendationsPrioritised next actions.
- Evidence AppendixAudit trail and supporting detail.
Runtime Governance Executive Reports™ are part of the platform, not an add-on. They are included as part of Managed Governance Partner™, Limited Pilot™, Enterprise Integration™, and Annual Runtime Governance Licence™ engagements. See a sample report →
From discovery to enterprise licensing.
The path a partner takes a customer through — and where the relationship compounds.
- Discovery
- Partner qualification
- Partner Discovery Workshop™
- Technical validation
- Limited Pilot™
- Partner onboarding
- API integration
- Customer deployment
- Monthly executive reports
- Renewals
- Expansion
- Enterprise licensing
Assets to take to market.
Download what’s ready; the rest is available on request during onboarding.
Architecture diagrams
Integration, deployment, and verdict-flow diagrams.
On this pageSales deck
Partner-facing pitch and positioning.
On requestCompliance mappings
EU AI Act, SOC 2, ISO 27001, NIST alignment.
On requestDemo videos
Engine in action: ALLOW / BLOCK / ESCALATE.
On requestAPI documentation
Endpoints, schema, auth, and adapters.
On requestCase studies
Representative deployments and outcomes.
On requestAnswers before you ask.
The questions partners raise most. The full FAQ covers 60+ across general, technical, and commercial.
General
What does Resurrection Tech actually sell?
Runtime governance infrastructure, evidence, deployment support, monitoring, updates, and commercial rights to use the governance layer — not unrestricted source code.
How does Runtime Governance work?
Every proposed agent action is evaluated before execution and resolved to ALLOW, BLOCK, or ESCALATE, based on whether its reachable trajectory intersects forbidden states (Ω).
Why do customers buy it?
To deploy autonomous agents safely, evidence governance for regulators and boards, and prevent catastrophic actions before they execute.
Why does a partnership make sense?
Your customers are adopting agentic AI in environments you already secure, advise, or operate. You add governed AI without building the technology.
Do customers keep working with us or with Resurrection Tech?
With you. For Managed and Channel models you own the relationship; governance runs behind the scenes.
Can we white-label?
Embedded/OEM white-label rights are available under licence and are determined during partnership discovery.
Who owns the technology?
Resurrection Tech retains ownership of the engine, governance logic, IP, updates, and infrastructure regardless of deployment location.
How quickly can we get started?
A discovery call, then onboarding. Hosted-API validation can begin quickly; full enablement follows the engagement plan.
Technical
How long does integration take?
It varies with how cleanly the framework exposes tool-execution hooks, the auth model, streaming vs request/response, and deployment constraints. Stacks close to our contract integrate quickly; others take longer. We scope each as an engineering estimate.
What does integration actually require?
A thin adapter that normalises the framework's tool calls into one contract; the engine returns the verdict. Anything that can make an HTTPS POST can connect.
What deployment options exist?
Hosted API, customer cloud (AWS/Azure/GCP), private cloud, on-prem, embedded SDK, and network proxy/sidecar.
Can customers stay on the hosted API?
Yes — it is the fastest route and fully supported. They can move to customer-hosted or private deployment later.
How does authentication work?
API keys for hosted; environment-appropriate auth (keys, OAuth, mTLS) for customer-hosted and private deployments.
What happens if the API is unavailable?
Fail-mode (fail-open vs fail-closed) is an explicit governance decision configured per deployment, with health checks and fallbacks.
What evidence is collected?
A tamper-evident audit trail of every decision, plus the metrics that power the monthly executive reports.
Do you support MCP and agent SDKs?
MCP and agent-SDK adapters are on the roadmap; today we support hosted-API integration plus framework adapters (LangChain, OpenAI Agents, Anthropic tool use, Bedrock, Azure AI, custom).
What about latency?
The engine decision is sub-millisecond; the practical budget is the network round-trip, which embedded/private deployment minimises for latency-sensitive flows.
Commercial
How does the commercial model work?
Typically partner onboarding (one-time), annual platform access, and per-customer commercial bands, with a minimum annual commitment. Specifics depend on the model.
Is onboarding a discount?
No. Onboarding is strategic enablement that prepares you to sell and deliver; customer engagements continue through the standard ladder, unchanged.
Who invoices the customer?
In Managed and Channel models, the partner invoices the customer and keeps the relationship. Other models vary by agreement.
How do renewals work?
The partner leads renewals; the monthly executive reports provide the evidence that supports them.
How do executive reports fit commercially?
They are included with Managed Governance Partner™, Limited Pilot™, Enterprise Integration™, and Annual Licence engagements — not priced separately.
When does commercial review apply?
For embedded/OEM/enterprise licensing, white-label, exclusivity, territory, and large-scale or sovereign deployments.
Is exclusivity available?
Exclusivity is never automatic. It is time-boxed, granted against a minimum annual guarantee, and carved out for direct and named accounts.
Do you sell direct as well?
Yes — Resurrection Tech retains the right to sell direct; deal registration and named-account exclusions protect partner-sourced deals.
What is the minimum commitment?
Most ongoing models carry a minimum annual commitment, confirmed during commercial review.
Ready to move forward?
Tell us your model and your customers, and we’ll scope onboarding and a go-to-market plan.