Frontier Bid is a marketplace for approved secure frontier runs. Sellers expose bounded runner capacity, not raw Codex or Claude accounts. Buyers receive reviewed artifacts from restricted coding runs.
Live MVP console
Operate the approval loop.
Run refresh first. API responses and errors appear here.
Task board
Postgres-backed run state
No tasks loaded.
Create task
Seller approval
Runner dry-run
Live MVP flow
The market board is gone. Only the executable loop remains.
The page now exposes the same task lifecycle as the deployed API. The data you see after refresh comes from Postgres, not bundled page data.
Create task
The buyer-side request becomes a pending seller-approval task with source bundle metadata.
Approve
The seller gate pins task class, runtime cap, command profile, network profile, and bundle hash.
Run
A runner can poll only approved tasks, claim one, execute in a prepared workspace, and submit an audit receipt.
Review
The submitted result and receipt are persisted for later buyer review and settlement work.
Buyer flow
Post work, buy the artifact.
A buyer posts a scoped task class, pins the artifact contract, reviews available sellers, then receives a signed run package with audit metadata.
Seller flow
Approve bounded runs.
Sellers choose a self-hosted, guided, or managed runner tier. Runner claims should only start after seller approval and source bundle preparation.
Trust controls
Approval gate
liveApproved tasks are the only tasks exposed to runner polling.
Source bundle hash
liveApproval and result submission must reference the same bundle id and SHA-256.
Audit receipt
liveResults require run metadata including runner id, claim id, duration, command profile, and artifact hash.
Runner tiers
Seller protection changes the fee model.
Managed isolation can cost more because Frontier Bid takes on more execution responsibility. Self-hosted remains the trust baseline.
Self-hosted locked runner
lowest feeseller-owned compute
The seller keeps credentials and compute behind their own boundary while the platform controls task lifecycle state.
Guided isolated runner
medium feeseller-owned or leased compute
The platform supplies the runner template and hardening checklist while the seller still owns secrets.
Managed isolated runner
highest feeplatform-operated compute
The platform operates ephemeral runners and charges more because it accepts more execution risk and infrastructure cost.
Settlement