What you want to know before your first run

Result and flow

Does Anvil Coder merge automatically?

No, the result arrives as a draft pull request in your repository, and a human merges it. How much you want to approve during the run is a per-project setting.Details: Review and supervision

Which checks actually run?

Guardrails on every step, a consistency pass at the end and, with your project’s toolchain, build and tests in the sandbox. Whatever could not be checked shows up as “unverified” in the run report instead of as green.Details: Build and verification

What does the organisation subscription include?

One Team subscription per organisation with ten seats in the base price and 75% of the base as runtime credit for your runs. Model costs with your own key are settled directly with the provider.Details: Plan prices and conditions

What do I get at the end?

A repository with history: every work step leaves its own commit, and you read on the commit which assignment it came from. The draft pull request lands where you review anyway.In detail: Integrations: the result is a repository

Which languages and frameworks are supported?

Java with Spring Boot is the most thoroughly proven path; any other stack you describe in a stack profile with language, versions and check commands. Build and tests run wherever the project’s toolchain is available in the sandbox.Why no list: Frameworks: what a stack profile contains

What if the result is no good?

During the run, the consistency pass sends affected steps into capped repair rounds; afterwards, a comment on the pull request becomes a follow-up run. You write what is missing instead of rebuilding it yourself.The flow as a whole: How it works: phases and slices · Integrations: the feedback channel on the pull request

Does this replace my review?

No, it makes your review shorter. Whether the requirement is right and the solution fits the problem is your call on the draft pull request; the system has checked consistency before you see it.What guardrails do and do not do: Guardrails: what they do not do

Trust, data and control

Who sees my code?

Your organisation is part of every record and every request, and the result sits in your private repository. What goes into the prompt is seen by the model provider you choose.The boundaries in detail: Security: the boundaries

Does it run in Switzerland?

Yes, the service runs on the Infomaniak Public Cloud in Switzerland. Model requests go to the provider you configure, and the result goes wherever your repository lives.Where the data lives: Security: where the data lives

Can I use my own model keys?

Yes, each organisation stores its own key and settles directly with the provider. For the Claude models it is even required: without it, no run starts.How it is stored and what it costs: Security: your organisation’s key · Pricing: what comes on top

How do I keep control?

Supervision is a per-project setting: from “every action needs an approval” to “only the consequential ones”, or no intermediate approval at all. The merge stays with you either way.Why that is the real question: For product teams: hand over the execution, keep the decision

Getting started, connectivity and cost

How do I start?

Create an account, connect your organisation to GitHub, register a project with a repository, move a ticket to the trigger state. There is no start button; the ticket is the assignment.What the system docks onto: Integrations: the order comes from the ticket · Pricing: organisation subscription

Do I need YouTrack?

No, the internal board in the cockpit is enough; YouTrack, Jira Cloud, GitHub Issues and GitLab Issues are options for teams that already work there. From the first pull request on you can stay there too and steer with a comment.Both channels side by side: Integrations: the paths in · Integrations: the shared default instance

What does it cost?

One Team subscription per organisation, with ten seats and runtime credit for your runs included; anything beyond that is metered. The introductory prices are on the pricing page and may still change before launch.The tariffs and their status: Pricing: organisation subscription · Pricing: status of this page

What does a mishap cost me?

As much as you cap: one ceiling per organisation, per project and per run, and the tightest one stops the run before it breaks the amount. Every project shows you what it has cost.How the three levels work: Operations: what can be capped

Your question is not here?

Write to us with what you want to know and one sentence about your project. Questions about operations, data sovereignty and billing are fastest resolved in a conversation; questions about the flow are best answered on a real story from your backlog.