Diavi

Diavi · From request to review

From the need to the merge request, a whole milestone at once

Diavi frames the project, designs the screens, writes the code, tests it and opens the merge request. You review, you approve.

See a demonstration How it works

No account, no commitment — real demo data, read-only.

A ticket's journey
Starting point A ticket or a milestoneLaunch an issue, or a whole milestone, from your repository.
  1. Reading the request
  2. Development
  3. Checks and tests
Merge request to reviewThe final decision is yours.

One request. A readable journey.

From launch to review, every step has its place. Diavi prepares the work; you keep the decision.

01

Read the request

Diavi reads the ticket or milestone and its context.

02

Produce the code

The request becomes a code proposal.

03

Check and test

The work goes through the verification steps.

04

Open the merge request

You review the proposal and you approve.

For those who build, steer and design

Same project. Three ways forward.

Development

Prepare the code, keep the review.

Start from a precise issue. Rerun, inspect the result and review the merge request in your Git workflow.

Project management

Carry the request through to work you can review.

Describe a need: Diavi draws the vision, the lots and the user stories from it; you review and approve them before they go to the forge. Roadmap, acceptance and starting in an empty repository follow in the same place.

Design

Show the screen before coding it.

A design system drawn from the vision, then clickable HTML mockups you annotate zone by zone. An approved mockup is attached to the issue, and the agent that writes the code reads it.

Clear tracking

A visible result. A clear next decision.

Issues, runs and diagnostics stay in one place. Copper guides the action; the status explains the result.

Diavi · Personal space / RunsDemo data · read-only
Examine before rerunningFailed
Issue #18 · acme/crm Set up an hourly cron to update third-party records Last run · 41 s · 4 days ago
Examine the runOpen the issue
History · 30 days · 6 runs 1 success5 failures16.7% success
To clarify Issue #16 Fix the linter violations

The request needs more detail before another run. Find the context in the Git issue.


Clarify → refresh → launch

“To clarify” is neither a failure nor finished work.

Illustrative preview, based on the read-only demo: no real figures.

Review stays human

Diavi proposes. You decide.

Generated code is work to examine, not an automatic approval. You review the merge request and choose what happens next.

Explore the demo

  • A clear request

    Expected criteria and context give the run a starting point.

  • An accessible diagnosis

    A failure is a run result to examine before another attempt.

  • An explicit approval

    A successful run does not mean the merge request was merged. Your main branch is never touched.

Your AI provider

Your own key. Separate costs.

You use your own Claude, OpenAI, Gemini, Mammouth or Ollama API key. Model calls stay on your side, and you keep full control of them.

The Diavi subscription does not include AI provider costs.

ClaudeOpenAIGeminiMammouthOllama

Your API key → the Diavi pipeline


Diavi orchestrates the journey from issue to merge request; model usage is separate from your plan's run volume.

Monthly plans

Choose your volume of work.

You pay for the volume of work delivered: a number of runs per month, each taking an issue to a reviewed merge request.

Développement

Monthly

€119 / month

To turn issues into code proposals to review.

  • 30 runs per month
  • Up to 2 at a time (fair use)
  • Development: issue → merge request

14-day free trial, no card required

Get started

Fair use · AI provider: your own Claude, OpenAI, Gemini, Mammouth or Ollama API key.
Model costs are not included in the subscription.

Start by looking, not by committing.

Explore issues, runs and their results in a read-only demo. Or read the public API to understand the integration.

Good to know

Answers, with no extra promises.

Can I see Diavi without creating an account?
Yes. The demo is open without an account or commitment. It shows real demo data, read-only.
What can I launch?
A ticket or a whole milestone. Diavi reads the request, produces the code, checks it, tests it and opens a merge request to review.
Do I need all three products?
No. Development, project management and design are taken separately. Together, they plug into one another: the vision feeds the mockups, and the mockups feed the code.
Can Diavi start a project from scratch?
Yes, from project management. In an empty repository, Diavi lays an application base — React, Vue.js, Laravel, Symfony, Node.js or Python — shaped by the vision and the design system, delivered as a merge request to review.
Who approves and merges the work?
You. Diavi never touches your main branch: the final merge request stays a human decision. If you turn it on, a standalone issue that reaches your threshold can be merged into a working branch.
Are model costs included?
No. You use your own Claude, OpenAI, Gemini, Mammouth or Ollama API key. AI provider usage is separate from the Diavi subscription.
How does the trial work?
Plans come with a 14-day trial, no credit card. Développement: €119, 30 runs per month ; Complet: €229, 120 runs per month.
Where are the API and help?
The public API reference and the Help centre are reachable from the navigation and the footer, without an account. An MCP server also lets you start and follow your runs from your coding assistant.

Your next issue deserves a proposal to review.

Discover how Diavi works, then choose the run volume that fits your work.

See a demonstration Choose a plan

Demo without an account · 14-day trial, no credit card