Choose the next product decision

Implement Agents now, or shape an Objects and Workforce early preview.

Agents is the current implementation path. Objects and Workforce are request-only early previews. Start with one product, one real job, and one decision boundary; every path uses the same application form below.

Choose a product path Run Agents independently

Agents is open source, with its first stable release coming soon. Objects and Workforce are available through focused early-access collaboration.

Three products · two engagement modes

Do not evaluate three maturity levels as if they were the same offer.

Current implementation

Awaken Agents

Run the product independently or scope one Agent application inside an approved infrastructure boundary.

Bring
One working Agent application, its client path, model and resource inputs, environment, and technical owner.
First decision
A scoped 4–6 week implementation uses 2–4 release checks, including a permission decision and interruption-and-recovery path, to reach a go, change, or stop decision.
Current boundary
Further hardening, integrations, rollout, and support require a new bounded service scope on the same Agents foundation.
View Agents → Review implementation detail → Discuss an Agents implementation →

Early preview

Awaken Objects

Shape a preview around one business fact and the system that already owns it.

Bring
One business object, its source authority and provenance, one governed change, and the application or Agent that consumes it.
First decision
Decide whether a shared typed-object boundary fits the job and which source connection or governed action a preview should validate next.
Current boundary
This is product discovery for an unreleased preview, not an Agents implementation, production commitment, or availability promise.
View Objects → Review the object model → Request an Objects preview →

Early preview

Awaken Workforce

Shape a preview around one recurring outcome that must survive hand-offs and exceptions.

Bring
One real job, responsible owner, execution systems, human decisions, exception path, evidence, and external acceptance fact.
First decision
Decide whether the Issue, responsibility, and acceptance model fits the job and which end-to-end loop a preview should validate next.
Current boundary
This is product discovery for an unreleased preview, not a packaged workflow, Agents implementation, or production commitment.
View Workforce → Review work and acceptance → Request a Workforce preview →

One intake · product-specific next step

The form is shared. The promise is not.

Every request starts with one product and one real job. We then route it according to current maturity instead of forcing preview requests through the Agents implementation story.

  1. 01

    Name the job and decision

    Describe the current baseline or loss, the responsible owner, the systems involved, and the first result another person or system can accept.

  2. 02

    Match the current product path

    Agents may lead to self-service evaluation or a scoped implementation. Objects and Workforce lead to product-specific preview discovery.

  3. 03

    Freeze one next step

    We reply with a supported self-service path, focused questions, or a bounded scope. No form submission automatically commits either team to production delivery.

Agents implementation scope does not transfer to Objects or Workforce. Preview interest does not imply product access, release timing, production readiness, support, or SLA.

Discuss implementation

Bring one product, one real job, and one next decision.

Choose Agents, Objects, or Workforce above. Describe the current work, authority and systems, the first accepted result, and what blocks the next decision. We aim to reply within one business day.

Prepare these four facts

  • ✓The selected product and one concrete job
  • ✓The current baseline, loss, or decision blocker
  • ✓The systems, data, identity, and execution boundary
  • ✓The buyer, operator, and acceptance owner
Optional systems, risks, and timing