Bo a Wɔbɔ ho FAQ

Zof uses six layers: platform plan, product modules, usage meters, deployment footprint, enterprise controls, and services. Plans include monthly credits, and test runs draw on them. When credits run out, new runs are refused. Enterprise and secure deployment use custom contracts.

Integration titiriw ka ho fi Team. Integration a ɛkorɔn ka Business+ ho. Custom integration yɛ nea wɔkan wɔ Enterprise mu.

SSO, SAML, ne SCIM ka Enterprise ne Secure Deployment ho.

One test scenario that reached a result: pass, fail, or partial fail. Each uses 1.5 credits, and one with no result uses none. Parallel scenarios each count individually.

Yes. Each company has a monthly spending limit, and new runs stop when credits run out. Enterprise contracts can add budget limits and approval workflows.

Teams see usage in the dashboard. When credits run out, new runs are refused and completed results stay readable. There is no overage charge. Enterprise terms are set by contract.

Yes. Plans include 10 GB on Starter, 50 GB on Team, and 200 GB on Business. A per-GB charge past that is starting soon and doesn't bill yet. Enterprise storage is negotiated.

Not today. Fix billing is starting soon: a validated fix, where the patch applied and your repository's tests passed, will be priced per fix. Test runs are priced per scenario with a result.

System Graph titiriw ka Business ho. Graph a ɛkorɔn, sie, ne entity scale ka Enterprise ne Secure Deployment ho.

Zof Studio ka Enterprise ne Secure Deployment ho. Business adefoɔ betumi de development nhwɛsoɔ a wɔhwɛ so aka ho sɛ add-on.

By validated fixes: the patch applied and your repository's tests passed. Failed attempts are never billed. Fix billing is starting soon.

Yiw. Ɔdefoɔ private cloud deployment yɛ enterprise nneɛma a wɔbɔ ho boɔ denam deployment kɛseɛ, environment, runner, graph scope, support, ne sie so.

Yiw. On-prem control plane ne runner fleet wɔ hɔ wɔ Secure Deployment ase a ɛwɔ deployment-based boɔ ne dwumadie service.

Yiw. Secure Enclave Runner foa signed execution capsule, local adansedie, ne egress a wɔapene so ma network a wɔaka so.

Yiw. Secure Deployment kura data hwɛ, sie, egress, SLA, ne dwumadie nhyehyɛe a wɔayɛ pɛ ma environment a wɔhwɛ so.

Enterprise kontrakt betumi de bring-your-own-agent akwan a wo agent yɛ adwuma wɔ Zof governance ne execution hye mu aka ho.

Enterprise ne Secure Deployment adefoɔ betumi de model endpoint a wɔapene so adi dwuma sɛ ɛhyɛ governance, data hwɛ, ne kontrakt nhyehyɛe ase.

Yes. Enterprise contracts can anchor on application footprint and test volume instead of seats alone.

Yes. Test runs are the primary volume driver for many contracts.

Yiw. Afe ne mfe pii enterprise kontrakt yɛ nea ɛyɛ pɛ ma Business, Enterprise, ne Secure Deployment.

Yiw. Starter ne Team foa pilot; Enterprise ne Secure Deployment taa fi pilot a wɔakyerɛ wɔ application a wɔapaw so ase.

Yiw. Enterprise adetɔn ma banbɔ nkrataa, DPA, nsɛmmisa, ne architecture nneɛma ma procurement.