$100 fixed. Seven days. One tenant. One bounded, non-critical synthetic workflow.
Use the smallest paid engagement to decide whether CarryFrame's execution record removes a real evidence-review burden. If it does, the first five eligible teams can continue into the existing $500 four-week founding pilot. Neither option is a production service or compliance certification.
Public reference permission is not required. After successful technical acceptance, CarryFrame may separately request optional organisation-name-only permission; read the boundary. Nothing is charged or accepted on this page.
Two deliberately bounded engagements
Start with the smallest useful scope.
$100 evidence check
Seven days, one tenant, one synthetic workflow, at most 250 recorded events and up to two hours of scheduled evidence-review assistance. It answers one pre-agreed reviewer question and does not consume one of the first five founding-pilot places.
$500 founding pilot
Four weeks, one tenant, one synthetic policy worksheet, at most 2,000 recorded events, reviewed principal enrollment and up to 12 hours of scheduled integration and evidence-review assistance. One kickoff and one honest-feedback session are within that cap.
Existing path only
The runnable client example and existing agentgateway reference echo-tool path. Any model dispatch needs a separately estimated and approved spend ceiling. No new target, gateway, provider mode or customer-specific platform feature is included.
Not included
Production dependencies, sensitive or irreplaceable data, legal advice, certification, penetration testing, guaranteed model accuracy, an uptime or recovery SLA, or 24/7 support. There are no automatic overages or renewal.
What a successful evaluation demonstrates
The agreed recorded path requires authenticated principals and explicit authority.
Initial and overridden decision versions are retained, with attributable reviews and halt/resume activity.
The agreed workflow exports a contiguous signed record that the standalone verifier accepts without a CarryFrame account.
Changing a signed record without re-signing causes verification to fail.
These are technical acceptance criteria, not a promise of business ROI, accurate model answers, an endorsement or third-party audit signoff. You supply an authorised sponsor and reviewer, safe synthetic inputs, a secure credential/export store and an approved integration environment.
A build-or-buy decision, not a lock-in exercise
Compare an implemented baseline before you commit.
CarryFrame does not claim these mechanisms are impossible to reproduce. The pilot gives your reviewer one working baseline for authenticated identity, explicit authority, retained raw versions, ordered event history, in-path tool recording, context succession and an offline-verifiable signed export.
At the end, keep the agreed export, verifier and trusted verification material. Compare the observed integration effort, review usefulness and operating limits with your internal build. Continue only if CarryFrame removes a real burden; otherwise stop after the fixed evaluation with no subscription or automatic renewal.
Evidence snapshot / 14 October 2026
Measured, not assumed.
Run a fresh bounded demonstration in your browser. The qualified public workflow completed 23 fixed steps, including five expected denials, two real model executions in successive contexts of one persistent role, two retained raw versions and zero fabricated human reviews. Its 17-event signed export verified offline; changing the exported record caused verification to fail.
The public demonstration uses synthetic data and one reference echo tool. It tests CarryFrame's recorded path and shared bounded capacity. It is not a customer workflow, an availability guarantee or evidence that external actions are captured.
A bounded hosted integration recorded 23 requests and 22 consecutive events: two model executions, one tool invocation, two record reviews, an override, escalation, halt/resume and one qualified context succession. It retained both raw decision versions, with zero unexplained event-sequence gaps or unattributed events in that fixture.
The full workflow used a private API fixture connected to the permanent database, gateway and protected worker. Public identity, gateway routing and signed export were separately verified. It was not one all-public end-to-end run. The original failed receipt observer and its read-only reconciliation remain in the evidence pack.
The sample's original export verifies offline; a deliberately altered copy fails. This procedure has run in a credential-free process, not yet in a commissioned independent human review. Read the published verification procedure. Download the synthetic reviewer example (ZIP) to inspect the unchanged export and offline verifier without an account. The full pilot pack remains available on request.
Reference boundary / 14 October 2026
Prove value first. Ask for a reference afterwards.
The $100 evidence check is a separate paid diagnostic; it neither consumes nor reserves a founding-pilot place. The $500 fixed fee applies to the first five signed eligible pilot agreements. Public naming is not a condition of either price, service or technical acceptance. A pilot slot is allocated only on the $500 pilot agreement's signature. Every fee and start date requires an executed agreement; this page is not a checkout or a binding acceptance mechanism. Later pilots require a separate quote.
No permission in the pilot order
Signing the pilot order grants CarryFrame no right to publish the customer’s name. CarryFrame must not identify an organisation as a prospect, pilot participant or customer without separate written permission.
Optional request after successful completion
After both parties record completion of the agreed technical acceptance, CarryFrame may invite the customer’s authorised signatory to grant a separate organisation-name-only permission. Declining or ignoring the request has no adverse consequence. Any permission must specify the exact approved name, factual wording, channels, dates and removal procedure.
Anything more requires separate approval
A name-only reference must not imply production adoption, successful results, regulatory compliance, certification or endorsement. Logos, employee names or images, quotations, case studies, confidential workflow details, exports and performance claims require separate express written approval of the specific material.
No organisation is being named as a customer on this page. This is a commercial boundary, not a legal opinion.
Exit with a verifiable record.
Export and verify the final revision, hand over the bundle and separately trusted key, stop execution and disable pilot access. Cancellation is not deletion. Normal raw-record retention has a six-calendar-month floor; the term and any applicable-law exception must be agreed before data admission. Eligible scoped deletion requires the authorised path, grace period, quiescence, export and restore-archive checks, leaving an attributed tombstone.
There is no promise of immediate or complete tenant-wide erasure: customer-held exports and control-plane traces are outside scoped payload deletion, and restore archives can block purge. The current permanent database is in US West; EU-only residency and zero-knowledge handling are not offered. Do not put secrets into task payloads. Support is scheduled and best effort, not continuous.
One workflow, one evaluation
Tell us what you need to demonstrate.
Email hello@carryframe.com or message CarryFrame on LinkedIn with your organisation’s name, your role, a brief non-confidential workflow description and the evidence your reviewer needs. Public reference permission is not part of qualification. Do not send credentials, raw customer records or sensitive data.
This page has no application form, analytics or tracking script. The email link opens your own mail application; the LinkedIn link opens CarryFrame’s third-party company page and may require a LinkedIn account. Nothing is sent until you choose to send it. An enquiry is not an agreement, a reserved place or automatic tenant access. Scope fit, signed terms and reviewed enrollment come first.
After qualification and a separately signed agreement, SmartTeddy Inc. issues the applicable one-off $100 evidence-check or $500 founding-pilot Stripe invoice for payment on Stripe’s hosted invoice page. Invoice identity, due date and applicable tax treatment are confirmed before issue. There is no subscription or automatic renewal. Payment alone does not grant platform access or any public naming permission.