FForklift
Explore verified sandbox

Commercial model

Scope first. Price the work before either side commits.

Forklift has not published a flat agent subscription. Model-routing cost, human review, connector work, service class, and recovery obligations must be measured before a recurring price can be defended.

Available now

Verified synthetic sandbox

Inspect the bounded sprint-metrics capability and its identity-bound governance path without connecting a customer system.

  • Synthetic data only
  • Verified Firebase identity in configured environments
  • A second identity required for independent approval
  • Production execution disabled until a durable worker exists
Explore the sandbox

Assessment first

Read-only operating assessment

Map the workflow, source systems, authority, data boundary, baseline, and stop conditions before proposing a build.

  • Written scope and deliverables
  • Controlled exports or process interviews first
  • Fee and any build credit agreed in advance
  • A valid outcome may be a documented decision not to build
Describe the workflow

Design partner

Governed capability build

For a candidate outcome that is not yet in the catalog, Forklift produces a reviewable implementation and operating proposal.

  • Exact tenant, data, and connector boundary
  • Named owners, approvals, and verification evidence
  • Build, managed-operation, recovery, and exit terms
  • Price and staffing stated before authorization
Start with Open Flow

Why there is no agent price yet

Usage economics are an engineering measurement, not marketing copy.

The proposed model-routing mix and index-task-equivalent multiplier remain hypotheses. Forklift will instrument trusted task producers, routing decisions, failed and partial operations, human review, and attributable cost before publishing included usage, overages, or margin claims.

What determines a written proposal

Data and authority

Classification, residency, tenancy, approval level, retention, and whether any consequential decision is involved.

Integration boundary

Controlled files versus connectors, system-of-record ownership, reconciliation, reversibility, and migration risk.

Operating obligation

Support window, service objective, observability, incident response, backup, recovery, upgrade, and teardown duties.

Evidence and economics

Approved baseline, success metric, implementation effort, trusted usage metering, review load, and measured delivery cost.

Bring one recurring workflow, not a blank check.

Open Flow captures the desired outcome and operating boundary. It does not authorize infrastructure, customer-data access, or execution.

Describe your workflow