Zara-first rollout

Start with Zara on the live assessment path. Use the waitlist when you need guided rollout access, guided onboarding, or private workspace activation.

Guided rollout access, not a public price grid

Start with Zara on /assess/, continue through /auth/, and reveal the authenticated pricing catalog only after sign-in. Public surfaces stay access-led during guided rollout.

Zara-first rollout. No public numeric prices during guided rollout. This page explains who the current rollout is for, how access works, and where plan selection actually happens.

Canonical first step
Start with Zara
Scope the first proof-backed workflow before any plan choice.
Assessment first
Best path for new teams in guided rollout
  • One public entrypoint at /assess/
  • Zara scopes fit, blockers, and the first proof path
  • Browser voice first, callback second
  • Leads directly into the canonical auth and onboarding path
  • Best fit when you want the first proof-backed workflow, not a brochure demo
Talk to Zara
Create the account
Plan selection and pricing are revealed only after sign-in.
Authenticated pricing
The real catalog lives inside the authenticated workspace
  • Canonical sign-in is /auth/
  • Authenticated catalog shows the active Workweaver and WorkMemory plans
  • Billing, usage, quotas, and invoice math stay in the same surface
  • Discounts apply inside the real product path, not on a fake public grid
  • Supports the same auth flow used for onboarding and runtime access
Open /auth/
Invited teams
Invite benefits remain real, but the public page stays access-led.
Benefits apply automatically
Create the account first, then the invite rules take over
  • Invite-based access stays compatible with the authenticated catalog
  • Human-readable invite benefits can be explained after sign-in
  • Checkout, entitlements, and invoices stay on the same truth path
  • Public visitors never need to decode coupon math before account creation
  • Best when an operator is already guiding rollout access
Use your invite
Internal access
Bitfoundry accounts remain complimentary during guided rollout.
Complimentary
No card, no public checkout, no separate backchannel
  • @bitfoundry.ai keeps the internal rollout path simple
  • Complementary access is handled in the authenticated flow, not on a public tier card
  • Useful for internal pilots, rollout QA, and support-led onboarding
  • Prevents the public route from implying fake general availability
  • Preserves one pricing truth even when checkout is bypassed
Sign in
Enterprise procurement
Security review, legal review, and rollout planning happen with a real human.
Contact sales
Procurement terms depend on the rollout and deployment shape
  • MSA, security review, and procurement handled directly
  • Dedicated rollout planning and operator alignment
  • Pricing and packaging depend on the real deployment surface
  • Prevents the public site from overpromising enterprise terms that are still operator-led
  • Support and legal contact stay visible on the public route
Contact Sales

What unlocks after sign-in. The authenticated workspace shows the real catalog, invite handling, usage, quotas, invoice explanations, and WorkMemory bundle truth. Public pricing stays intentionally access-led until guided rollout expands.

Common questions

Why are public prices hidden?

During guided rollout, public surfaces explain access and fit while the authenticated workspace shows the actual plans, usage terms, and billing math. That keeps the public route truthful even while invite handling and bundled WorkMemory terms vary by account.

Where do I pick a plan?

Plan selection happens after sign-in on the authenticated product path. Public visitors should use /auth/, not an older app subdomain or a public price grid.

How do alpha discounts work?

Invite benefits and other rollout rules are applied inside the authenticated flow. Public pages stay clear of coupon math so checkout, entitlements, and invoice explanations all come from one source of truth.

What happens for internal access?

Internal @bitfoundry.ai accounts remain complimentary during guided rollout, with the bypass handled inside the authenticated flow rather than on a public pricing card.

What proof do I see before I buy?

Start with Zara for the first workflow. The product is built around approvals, proof, and evidence-backed outcomes, so the rollout path is about verifying fit and the first proof loop, not pushing a public list price.

How does Enterprise procurement work?

We support PO-based procurement, custom MSAs, and security reviews. Reach out to hello@workweaver.ai and we will respond within one business day.