Skip to content

DevDispatcher

Your tickets become reviewed pull requests, in your own repository.

Dev as a Service (DaaS). A team of development agents picks up the ready tickets on your GitHub board, writes the code in your repository and delivers each ticket as a pull request that has already been reviewed.

Create your account, connect GitHub and create your first project in minutes.

The console

One place to watch the team work.

The console's Projects screen with sample data: the New project button and two projects of the fictional organization Orbital, each with its health, the agents working on it, the items waiting on you and the month's spend. The console's Projects screen with sample data: the New project button and two projects of the fictional organization Orbital, each with its health, the agents working on it, the items waiting on you and the month's spend.
Projects: the New project button and each project's health, the agents at work, what is waiting on you and the month's spend.

Product

A development team that follows your board and reports back in the console.

Each role is a separate agent, and the console shows what they are doing, what needs you and what has been spent.

  • Development

    Picks up the ticket, opens a branch and delivers a pull request.

  • Code review

    Reviews every delivery and sends it back to development when it needs changes.

  • Product owner

    Refines and prioritizes tickets and asks what is unclear.

  • You

    Approve what goes to production.

Your board is in charge

Agents start from what is ready, in the priority you set on the board, and move each card across your columns as they work. A ticket that is not ready goes back to triage with the reason written down.

Delivery management built in

A delivery manager assigns the work, reports progress and drafts the status update, which you edit before it is posted to the project.

What needs you comes first

Every project shows its health — on track, needs attention or critical — with the reason next to it, and pending decisions rise to the top.

Insights on spend and delivery

The month's spend, the cost per run and the tickets delivered per week, by project and by day.

Your knowledge, in layers

Agents follow your organization's and your project's working rules, kept in versioned repositories you own.

How it works

From sign-up to the first pull request, in four steps.

No agent works in your repository until you turn the project on.

  1. Sign up

    Create your account and your organization in the console.

  2. Connect your project

    Connect GitHub and install the service's apps; then the New project wizard connects your repository and board and shows everything it will set up before you confirm.

  3. Run a simulation

    The whole flow runs with test agents in a simulation repository, and 12 checks show how it behaved. Nothing is written to your repository.

  4. Turn the team on

    Set the capacity and the monthly limit and turn the project on. Every delivery arrives as a reviewed pull request.

Works with

Code
GitHub
Tickets
GitHub Issues and GitHub Projects
Branches
deliveries land on dev; production stays yours
Languages
English, Portuguese and Spanish

You control

  • The board: what goes in, the order and the definition of ready.
  • Turning a project on, pausing it or stopping development in progress; a review round already under way finishes on its own.
  • Slots per role, items in progress and each project's monthly limit.
  • Who approves what goes to production.

Safeguards

Isolation and governance by default.

These apply to every organization, from the first project.

Your organization only

Each organization sees only its own projects, and the server rejects any action on a project that is not yours.

Nothing starts by itself

A new project starts turned off, and none of its routines run until you turn it on.

A log that cannot be erased

Every confirmed action is kept — who, when, what changed and the outcome — and the console has no way to erase it.

Production stays yours

Agents deliver by pull request into dev and never push to your production branch.

The console's Capacity panel with sample data: the development and code review slots, each with its current value, the controls to change it and the limit. The console's Capacity panel with sample data: the development and code review slots, each with its current value, the controls to change it and the limit.

Pricing

Simulate the price of your team.

Choose a package or set a budget on demand, and see what it buys before you start.

  • Individual

    1 repository, 1 agent

    Price on request

  • Small team

    1 team, 3 agents

    Price on request

  • Small company

    3 teams, 6 agents

    Price on request

Or on demand: a budget per week or per month.

FAQ

What buyers ask first.

How do we start?

Click Get started, create your account, connect GitHub and create your first project with the New project wizard. Run a simulation, then turn the project on.

What does the service touch in our GitHub?

Your board, its labels and, in your repository, the agents' instructions file and a .gitignore block that keeps credentials out. Agents work on branches and deliver pull requests into dev; your application code changes only through those pull requests.

Who approves what reaches production?

You do. Every pull request is reviewed by the code review agent, and only a person on your team merges into production.

Which languages are supported?

This page and the console are in English, Portuguese and Spanish, and each person chooses their language in the console.

Who sees our code and tickets?

Your organization and the service. To do the work, the agents send your code and tickets to the model providers the service uses. In the console, each organization sees only its own projects, and the server refuses any action on a project that is not yours.

How is it priced?

By package or on demand, with a monthly limit per project that you set on the usage the service meters: when it is reached, nothing new starts. Ask Digitnix what the limit covers in your project. Prices are for new contracts; a signed contract keeps its price. Simulate the price.

Start with one project, and decide when the team starts.

Create your organization and your first project today. Its routines stay off until you turn it on, when you are ready.