Byte Enterprise · 2.4 preview
Shared work.
Explicit access.
Follow project work across coding agents while keeping company access, evidence and decisions accountable. Designed initially for engineering teams of 20–250 developers.
Controlled administration preview, enabled only for individually approved companies. Current access is limited to reviewing membership, roles and capacity, and revoking enrolled devices. Company work, collection, identity-provider activation, automation, provisioning and export delivery remain held. General availability requires provider verification, an independent security review and customer pilots. No release date or service-level commitment is promised here.
Enterprise design and validation targets
Administration does not mean access to every conversation.
- Project access you can explain
- Built-in and custom roles, teams, project grants and expiring guests define who can read, change or export work. Delegated administrators cannot grant beyond their authority.
- Protected source material
- A shared task or Work Trail does not unlock its private source sessions. Content grants have a purpose, scope and expiry, with sensitive access recorded.
- Company identity
- Per-company OIDC or SAML connections, passkey step-up, SCIM provisioning and session revocation. Entra and Okta interoperability must be verified in authorised test tenants before general availability.
- Policies and audit
- Review collection, sharing, approvals and retention policies. Sensitive operations require a durable audit record. Actual immutable archive storage must be configured and verified for the deployment.
Two editions, one product
The workspace sets the boundary.
| Capability | Byte Solo | Byte Enterprise target capabilities |
|---|---|---|
| Work and evidence | Personal tasks, sessions and Work Trails. | Authorised project artifacts with independently protected sources. |
| Access | Your personal workspace. | Roles, groups, scoped grants, guests and access reviews. |
| Identity | Existing personal sign-in. | Company identity connection, provisioning, step-up and recovery. |
| Commercial access | Scout $2, Operator $9, Max $19 per month. | Quoted contract and assigned named developer seats. Administrative roles do not consume a developer seat by themselves. |
| Automation | Existing tier and project settings. | Disabled by default. Permission, company policy, device grant and native capability must all allow an action. |
| Deployment | Local desktop and supported personal workflows. | Byte-managed shared or dedicated cells, subject to verified readiness. |
The Enterprise contract model separates named seats from permissions and personal plans. An assigned seat cannot enable held preview features. The table describes the intended Enterprise edition; these developer workflows are not available in the administration preview.
Company setup
A deliberate first connection.
-
Confirm the contract and region
Agree named-seat capacity, hosting and residency. Provisioning begins after authorised acceptance and confirmed settlement or approved credit terms. An unavailable region stays pending.
-
Establish company identity
The initial owner follows a single-use onboarding link, verifies the domain and tests the identity connection. Mandatory SSO requires recoverable privileged identities and tested emergency access.
-
Map teams and assign seats
Review directory-group mappings, project roles and automatic seat rules. Provisioned members without an assigned seat cannot use developer capabilities.
-
Enrol and review the device
Use a company device code in Byte, then review exact repository destinations. New company collection defaults to redacted content. Existing Personal history is not imported automatically.
-
Verify the complete lifecycle
Test a member joining, changing teams and leaving. Confirm access revocation, audit delivery and restore behavior before broad rollout. Unsupported native controls stay unavailable.
Deployment availability
Choose a verified destination.
India is the existing hosting region. US and EU cells are provisioned on demand and become selectable only after routing, isolation, backup, audit-storage and regional placement checks pass.
Dedicated Enterprise is operated by Byte. Customer-operated self-hosting, air-gapped deployments, customer-managed encryption keys and legal holds are outside this release.
Connected revocation targets 60 seconds; an offline desktop lease lasts no more than 15 minutes. Those bounds do not stop independently running external agents or erase files copied outside Byte.
Project-content residency does not automatically cover global billing, licensing or external identity-provider metadata. Contracted residency must identify the data it covers. Byte does not claim SOC 2 or ISO certification.
Discuss deployment requirements