pramaanStart a brief

Governed application capability platform

Build software
with agents.
Ship it with proof.

Pramaan brings requirements, agent execution, trusted capabilities, release control, and continuous maintenance into one governed system.

Start with a brief See how it works

Private pilot · Product foundation under active development

Illustrative governed release receipt
Illustrative release receiptverified
RUNPRA–042
SUBJECT SHA4f8a…9c21
  1. Brief
  2. Plan
  3. Build
  4. Gate
  5. 5Release
AuthorityBounded
Cost envelopeWithin limit
RollbackProved
Evidence setsha256:98c7…d451

Why Pramaan

AI made code faster.
It did not make delivery accountable.

Teams still lose decisions between a brief and a pull request. Agent runs inherit too much authority. Tests prove an unknown build. Deployment ends the story before the customer outcome is known.

Pramaan connects those pieces into a traceable lifecycle—while keeping the harness, model, cloud, and application architecture replaceable.

One platform · three ways in

Start at the layer
you actually need.

Foundry uses Loop. Loop can pull Pramaan Capabilities. Capabilities also stand alone. The customer chooses the entry point—not a different platform.

01

Pramaan Foundry

Pilot engagement

Build it with us.

A managed product-delivery engagement for teams that want the whole path: requirements, journey, architecture, phased build, release, and learning.

  • Managed delivery
  • Human approvals
  • Outcome ownership
02

Pramaan Loop

In development

Build it with your team.

The governed application-delivery lifecycle. Loop turns an approved plan into bounded agent work, exact-SHA evidence, safe releases, and observed outcomes.

  • Lifecycle control
  • Agent execution
  • Release evidence
03

Pramaan Capabilities

Foundation live locally

Use the primitives.

Governed APIs, SDKs, MCP tools, embeds, and generated integration surfaces—with identity, policy, metering, audit, and credential custody underneath.

  • APIs + SDKs
  • Builder Kit
  • Optional hosted runtime

The delivery loop

Definition is part of the build.

Loop begins before an agent touches code and stays present after production. Every step produces a contract, decision, or receipt the next step can verify.

Requirements map to journeys. Journeys map to acceptance criteria. Acceptance criteria map to bounded phases and release evidence.

Explore Pramaan Loop
  1. 01DefineBrief + PRD
  2. 02DesignJourney + architecture
  3. 03PlanPhases + envelope
  4. 04BuildCandidates + gates
  5. 05ReleaseDeploy + rollback
  6. 06LearnObserve outcome

Where agents execute

Isolated workers,
not the trust kernel.

A worker checks out the exact code, runs the chosen harness and skills, proposes a patch, executes gates, and returns receipts. The kernel governs authority, identity, metering, and evidence; it does not write application code.

Hosted or customer-hosted

Workers can run in Pramaan infrastructure or a customer-controlled GitHub/VPC environment. The protocol stays the same.

Pramaan execution plane architecture
Intent
01Human authorityObjective · policy · budget
02Pramaan LoopLifecycle controller
bounded work order→
Ephemeral workerisolated
01Checkout exact SHA
02Inspect + patch
03Test + review
04Return evidence
HarnessSkillsCost meter
proposal + receipts→
Delivery
03RepositoryPR · CI · approval
04Customer releaseCanary · observe · rollback

The trust layer

Proof is not a PDF generated at the end.

It is the shape of the system: exact identities, append-only records, constrained effects, honest state, and verifiable postconditions.

Read the trust model
01

Authority is explicit

Agents receive a bounded envelope: permitted work, scope, providers, time, cost, and escalation rules.

02

Every release has a subject

Plans, tests, approvals, and deployment evidence bind to the exact code and release digests they prove.

03

Recovery is designed in

Idempotency, reconciliation, canaries, and rollback are protocol concerns—not hopeful instructions in a prompt.

04

Cost follows the work

Provider receipts settle into a run and phase ledger, so customer cost comes from usage rather than guesswork.

Built in the open, claimed precisely

Strong foundation. Production proof still ahead.

The gateway, kernel, contracts, private execution boundary, durable Loop exchange, and adversarial local suites exist. Live Singapore deployment, first capability productization, and a customer pilot are the next proof points.

See the build status

Start at the beginning

Bring the objective.
Leave with a buildable brief.

Shape a brief