A phased plan, with its limits visible

Apply for the invite-only beta. A person reads every application. The beta began on 1 November 2026.

Public launch and the Community edition are targeted for 1 January 2027. Plans change; dates are targets, not promises.

Designed with ISO 27001 and SOC II in mind. Not certified. Audit readiness is planned for Q1 2027.

A planned, consented approach to organisation memory and a skills factory, with redaction on the device. It is a future direction, not an available capability.

Enforced organisation roles, single sign-on, Assure proof packs and Board edition readiness are planning themes. Confirm scope and evidence before relying on them.

Applications are invite only. Identify the business, first task, project owner and person authorised to approve. A more sensitive deployment also needs data classification, access review and agreed terms. Submission is not automatic acceptance or a committed start date.

Review the task, permissions, data-processing agreement, security evidence and operating support before rollout. A pilot should gather evidence before scope expands. The earlier guide's weekly quotas and customer milestones are not current commitments.

The earlier guide included financial scenarios and customer acquisition targets. They are not results and are not published here. Ask for evidence specific to a capability rather than inferring proof from a roadmap.

People can become approval bottlenecks. Platform approvals can delay channels. AI usage and support needs affect costs. A role description does not prove a working autonomous service. Agree escalation, spending limits and review ownership before relying on the beta.

People retain responsibility for business decisions, contracts and attestations. Deployment and liability terms must be agreed in writing. Customer-zero use is distinct from independent customer proof; no customer count or independent attestation is inferred.