Reqursor Development and Reqursor Platform are now one product.

See what changed

Reqursor. Hand it tickets, or just ask.

Technical teams hand it tickets. Anyone else describes a change in the AI chat. Either way, every change is checked first and waits for a person's yes. Online stores are in early access, by invitation.

01 Tickets

Hand it a ticket, or ask for a plan first.

Each ticket runs in its own copy of your repository. If a check fails, Reqursor tries to fix it, up to two times by default. If it still fails, nothing is committed: the ticket comes back with a plain reason, and you can retry it with a hint.

  • Ask for a plan: steps, open questions and a suggested split, with nothing changed in your repository
  • Read the change file by file, with the evidence next to each file
  • A screenshot of the running app before and after, if you want proof
  • Your design rules, written as text, guide every change people see
How a run works

02 AI chat

Ask in plain words, confirm what it drafts.

Ask it about your tickets, runs and settings. It drafts tickets, changes to tickets and small settings changes for you, and nothing happens until you press Confirm.

  • A draft expires after 10 minutes, and acts with the permissions of the person who confirms it
  • It never edits code, pushes or opens a pull request itself
  • Starting work from the chat stays off until an Owner or Admin switches it on

03 Online stores Early access

Change a store by describing it.

Say what you want changed, like the color of the buttons. It starts with colors and design settings. You see a before and after preview, and nothing in the store changes until you press Confirm and apply.

  • It never changes products, prices, coupons, orders or customers
  • Go back to an earlier version of the store's settings from the store page, with orders, customers and products left as they are
  • Early access, by invitation: today we show it to you in person
Ask for an invitation

04 Works with

Your stack, as it is.

Your git host and tracker, your AI provider, your languages and your servers. Where a plan decides, a tag says which.

Git and tickets

Import tickets with one click, or write them in Reqursor's own queue.

  • GitHub
  • GitLab
  • JiraTeam
  • LinearTeam
  • Own queue

AI models

Reqursor Credits need no key. Or bring your own.

  • Reqursor Credits
  • Anthropic
  • Google Vertex AI
  • Amazon Bedrock
  • Microsoft Foundry
  • Moonshot AIBeta

Runs on

Hosted by us, or on your own machine.

  • Hosted by Reqursor
  • Linux
  • Docker
  • Raspberry Pi 5
  • WindowsOwn machine

Languages

Any project that builds and tests from a command.

  • Node.js
  • Python
  • PHP
  • Go
  • Rust
  • Maven
  • Gradle

Notifications

Email on every plan.

  • Email
  • SlackTeam
  • WebhooksTeam
  • A draft pull request on GitHub, a branch on GitLab. A GitLab you run yourself works too; GitHub Enterprise Server does not.
  • Jira, Linear, Slack and webhooks from the Team plan. The pricing page has the rest.
  • Claude through Amazon Bedrock, Google Vertex AI or Microsoft Foundry uses your own key. Moonshot AI is a beta, for projects that opt in.
  • With your own key, AI requests go straight from your server to your provider. Hosted, they pass through our relay, which keeps no prompts or answers.
  • Setup proposes the build and test commands for the languages above. A digest email is there if you want one.
  • On Windows, use a machine of its own: the agent runs there without the isolation Linux gives it.

Every plan side by side, with everything it includes.

05 Control

The limits it keeps.

Beyond your checks and your yes: what Reqursor will not do on its own, and what stays on record.

  • It never merges by itself. Pushing stays off until you switch it on, and it reaches your main branch only in Fast mode, after you type the branch name.
  • Four roles decide who may do what: Owner, Admin, Developer and Viewer. Viewers follow along for free, without using a seat.
  • It refuses force pushes, history rewrites and protected branches.
  • Revert undoes a change with a new commit. History is never rewritten.
  • Every action, by a person or by an access token, goes in the audit log. Nobody can edit an entry.
  • Keys and passwords you add are write only and encrypted at rest. Nobody can read them back, the Owner included.
  • Instructions hidden inside a ticket cannot approve anything in the AI chat. Only a person can press Confirm.
  • On Linux, the agent can reach only the hosts on your project's allowlist during a ticket: the public package registries, by default.
How Reqursor handles your code

See it on your own tickets. Start with credits.

The starter license lasts 14 days, or until its credits are used up, and needs no API key and no account with a model provider. Or tell us about your team, and we show it to you.