TEMRAL
Menu

How TEMRAL works

Change one URL.
Keep everything that matters.

Point the same SDK at the TEMRAL base URL. Your provider choice, models, prompts, streaming behavior, and rollback path stay under your control. Each admitted result returns with measured savings and a cryptographic receipt.

Evaluate one workloadSee the workspace
Application change
Base URL only
Provider choice
Remains yours
Proof standard
Invariant by tier
One governed requestPOST /v1/chat/completions
Contract preserved
  1. 01
    Your applicationChange the base URL

    Keep the same SDK, payload shape, models, provider keys, and streaming contract.

    One change
  2. 02
    Same requestSend the workload

    Your application sends the request through the TEMRAL endpoint without a workflow rewrite.

    Unchanged
  3. 03
    TEMRALGovern the economics

    Policy and measured workload fit determine whether the request enters the agreed reduction envelope.

    Governed
  4. 04
    Chosen providerExecute normally

    The selected provider and model remain attributable while TEMRAL preserves the application contract.

    Bound
  5. 05
    Your applicationReceive result + receipt

    The outcome returns with measured cost, scope, integrity, and recovery custody in one record.

    Receipted
Input contractPreserved
Economic resultMeasured
Receipt integrityCryptographic
Evaluate one workload

The operating contract

You keep control of the product.

TEMRAL changes the governed cost outcome—not who owns the application, provider choice, rollout, or customer relationship.

BoundaryYour teamTEMRAL
Provider + model

You choose the route and may change it.

TEMRAL records the selected provider and model inside each governed run.

Workflow + payload

Your existing application contract stays intact.

No prompt, SDK, streaming, or response-shape rewrite is required.

Rollout + rollback

Your team retains deployment authority.

Start with one workload, pause safely, and return to the provider path whenever needed.

What gets measured

One economic event. Four explicit moments.

A percentage never upgrades the proof standard. It changes only the admitted reduction target for a workload that fits.

  1. 01
    Baseline fixed

    The agreed comparison basis is bound before a savings claim exists.

    Before
  2. 02
    Request governed

    The selected tier applies only where the workload fits its admitted envelope.

    During
  3. 03
    Outcome checked

    The returned result must clear the workload acceptance contract.

    After
  4. 04
    Receipt sealed

    Measured savings, scope, provider route, and integrity close together.

    Proof

Start with one workload. Keep the rollback path.

Evaluation binds the baseline, acceptance contract, tier, and scope before anything can become a savings claim.

Bring one workload