Byteflare for Enterprise

An Enterprise agreement covers everything in the Team plan, arranged under a contract that satisfies procurement, security review and finance.

Who this is for: Buyers, IT and security reviewers, and procurement teams evaluating Byteflare for an organisation.

Enterprise is not a plan you can buy from the pricing page. It is a contracted agreement, priced and scoped in a conversation, that sits on top of the Team product. This page sets out what is in the product today, what is arranged contractually, and what a security review will want to know.

In the product today

Governance and access control

Three roles — owner, admin and member — with server-side enforcement on every privileged action, not interface-only hiding.
Exactly one owner per organisation. The owner role cannot be granted by invitation or by a role change; it moves only through an explicit ownership transfer performed by the current owner.
Billing is restricted to the owner. Admins can run the workspace without being able to change what it costs.
Invitations are bound to a specific email address, are single-use, and expire after 7 days.
Seat limits are enforced when an invitation is created and again when it is accepted.

The complete permission matrix is published in Roles and permissions.

Tenant isolation

Workspace separation is enforced by row-level security policies in the database and re-checked in application code, so a request that bypasses the interface is still refused. An automated test suite asserts the isolation guarantees on every change, covering cross-organisation access by exact record id, member-role privilege escalation, users with no organisation, suspended members, and invited users who have not yet accepted.

Client-facing controls

Public proposal links are frozen snapshots, so the version a client accepted cannot be altered afterwards. That is an evidentiary property, not just a caching decision.
Links can be given an expiry of 7, 14, 30 or 90 days, or revoked immediately at any time.
The public document is built from a strict field allowlist, so no internal workspace data can leak through a shared link.
Acceptances record the date and the email address the client entered, against one specific snapshot.
Custom branding is organisation-level, so client documents carry your marks rather than Byteflare's.

Data handling during AI generation

Scope generation sends the brief text and your scoping settings to a third-party model provider over an encrypted connection. Byteflare records that a generation happened — the account, the endpoint and the timestamp — for rate limiting and diagnostics; that record does not contain the brief. The full statement of what is processed, on what basis, and for how long is in the Privacy Policy, and the practical version is in Privacy, data and AI.

Arranged in the agreement

These are the areas an Enterprise agreement is normally used to settle. They are handled with the Byteflare team as part of contracting rather than configured by you in the product:

Single sign-on through SAML.
Custom roles and permissions beyond owner, admin and member.
Audit logging and data residency requirements.
Unlimited seats under a negotiated commercial structure.
API access and custom integrations.
A custom contract, purchase-order invoicing, and a service level agreement.
A named account manager and assisted onboarding.

Answers a security review usually needs

Question	Answer
Who processes our payments?	Paddle, as merchant of record. Byteflare never receives or stores card details.
Is our data separated from other customers?	Yes, by row-level security in the database plus application-level checks, with an automated isolation test suite.
Does content leave your infrastructure?	Yes, for AI generation. Brief text and scoping settings are sent to a third-party model provider. See the Privacy Policy for the current statement.
Can a shared proposal be changed after a client accepts it?	No. Snapshots are frozen at creation; a change requires revoking the link and issuing a new one.
Can we revoke external access immediately?	Yes. Revoking a public link stops it working straight away, and removing a member removes their workspace access immediately.
Who can spend money on the account?	The organisation owner only. Enforced server-side.
What certifications do you hold?	Ask the Enterprise team. Byteflare does not publish certification claims it cannot evidence, and none are asserted on this page.

Procurement

Start the conversation
Tell us the number of seats, your timescale, the regions your data must stay in, and any control that is non-negotiable for your review.
Evaluate on Team
Most requirements around roles, isolation and client-facing controls can be tested directly on the Team plan before anything is signed.
Security and legal review
Send your questionnaire and your paper. We will answer what we can evidence and tell you plainly where we cannot.
Contract and invoicing
Enterprise agreements are invoiced under the contract rather than through the self-serve checkout.

Talk to the Enterprise team

Write to enterprise@byteflare.app. Include your organisation, seat count, timescale and the specific requirements you need confirmed, and you will get a substantive answer rather than a discovery call request.