Order Wharfly

Four decisions, then onboarding. The tier caps the number of parallel coders; model consumption is billed by usage, on top, unless you connect your own accounts.

Tier

Starter 1 coder · 2 simultaneous tasks · 1 project, 1 repository · 2 users · security audit 99 $/ month Promost common 2 parallel coders · 4 tasks · 5 projects, several repositories · 10 users · security + architecture audits · multi-repo groups · canary with rollback · SIEM export 199 $/ month Enterprise 3 coders · custom sizing · custom severities · per-repository model restriction · code analysis included · single sign-on · phone support On quote

Billing period

Monthly Yearly

Yearly: discount to be set — the summary shows the monthly price × 12 until it is set.

Model provisioning

Wharfly modelsNothing to subscribe to. A capped, revocable virtual key, one invoice. Consumption billed by usage, on top of the tier. Your own accountsYour API keys, your plans, or your self-hosted models. None of the consumption goes through our invoice. Connected at onboarding, per provider — API key or OAuth link depending on the provider. A mix, per providerThe choice is made provider by provider, and changed later without touching your repositories.

The summary is computed by the server: every change of tier, period or provisioning is applied with this button. No step of this journey needs JavaScript.

Summary

Tier: Enterprise
Parallel coders: 3
Period: —
Models: Wharfly models
Subscription: On quote
Applicable taxes: to be set

Model consumption is billed by usage, on top of the subscription, from a dated price grid. The cost per accepted deliverable is shown in the portal.

Request intake is not connected on this instance: sending is disabled rather than losing your request silently. to be connected

By ordering you accept the terms of use to be written. Cancellable at the end of the current period; the result lives in your git, there is nothing to migrate.

What happens next

Your server is provisioned and attached to the account.
Your model access is connected, per provider.
Your repositories are described: commands, default branch, sensitive paths.
A first workflow is composed, dry-run, then tried on a sandbox repository.

Typical duration: to be set

A question before ordering?

The tier can be changed later; what changes badly is a vague specification. A scoping interview consumes no task.

Ask a technical question