Reqursor Development and Reqursor Platform are now one product.

See what changed
Contact sales

Your AI software maintainer.

Reqursor takes on the IT work your team never gets done.

Contact sales Start now
Run it on your own server

In: a ticket or a chat message. Out: a checked change.

Import a ticket from Jira or GitHub, or type what you need in the chat. Reqursor makes the change to your code or your online store, checks it, and waits for your yes.

Example chat request, about 12 seconds

Ticket from Jira

Add a health check endpoint

Written by your team in plain words.

  • It answers with a 200
  • It shows the app version
  • A test covers it

Sandbox

Your checks run first.

  • Build
  • Lint
  • Typecheck
  • Tests

Stopped. Nothing half-done is committed.

Working in a sandbox, away from your live code.

Result

Draft pull request

Add a health check endpoint

  • It answers with a 200health.ts, line 12
  • It shows the app versionhealth.ts, line 14
  • A test covers ithealth.test.ts, line 6

Waiting for your team.

Back with your team, with a report of what was tried and why it stopped.

Chat

You: Make the sale banner pink and put it above the products.

Reqursor: I can do that. You see a preview before anything changes.

  • The banner turns pink
  • It moves above the products
  • Products, prices and orders stay as they are

Preview

Checked before you see it. Before

  • Settings
  • Layout
  • Preview

Stopped. Nothing is applied to the store.

Shown as a preview, away from your live store.

Result

Store change, ready to apply

Pink sale banner above the products

  • Banner colorfrom gray to pink
  • Banner positionnow above the products
  • Products, prices and ordersuntouched

Waiting for your confirmation.

Back in the chat with the reason it stopped. Your store is unchanged.

Nothing goes live until you say yes.

A simplified demo with two example requests. Not a recording of the live product. Changes to online stores are in early access.

Works with what you already use.

Bring tickets from the tracker your team uses, or ask for them in the AI chat. Reqursor works in the repository you already have and runs the checks you already trust.

  • Import tickets from GitHub, GitLab, Jira or Linear with one click
  • Or ask in the AI chat and confirm the draft ticket it writes
  • A draft pull request on GitHub, or a branch on GitLab
  • Your own build, lint, typecheck and tests decide what passes
See which plan includes what

Jira and Linear on the Team plan. The AI chat also takes online store changes, in early access.

You decide what goes live.

Every change is checked first, shown to you in full, and waits for your yes. The same three rules for your code and your online store.

Checked before you see it.

Your own build, lint, typecheck and tests must pass, then a second review in a fresh session and a security scan.Settings and layout checks run first, then a preview is built for you to look at.

How a run works

You see exactly what changed.

The change itself, with every acceptance item of the ticket linked to the lines that meet it.Before and after, side by side. Drag the line to compare them.

Watch the example run

Nothing goes live without your yes.

Reqursor hands back a draft. Your team merges and releases it, with your own tools.You press Confirm and apply. Until then nothing in the store changes.

How Reqursor handles your code

It never changes your products, prices or orders, and it never deploys your code.

It also finds the work.

Bug Hunt and Maintenance look for problems on their own and file each one as a draft ticket in your queue. By default nothing starts until you approve it.

Bug Hunt

It clicks through your site and writes up what breaks.

On a schedule or when you press Scan now, it opens your staging site in a browser and clicks through it. Each error becomes a draft ticket with the steps to repeat it and a screenshot.

How Bug Hunt works

Maintenance

It keeps an eye on your dependencies.

It checks for outdated packages, security advisories that affect them, or a command of your own. These checks make no AI call, so a run costs nothing.

See the maintenance checks

Autopilot

You approve. Autopilot can start the work.

Approving moves a draft ticket to Ready. With Autopilot on, the top ready ticket starts whenever the project is idle, within your working hours and budgets. When nothing is ready, it switches itself off.

How Autopilot works

Hosted by us, or on your own server.

The same Reqursor either way. You choose who runs it, and who you pay for the AI.

Hosted by Reqursor

We run it for you.

Nothing to install or keep updated. After you buy, Reqursor sets up your dashboard and emails you its address. The AI work is paid with Reqursor Credits, so you need no API key.

  • Your own dashboard at yourteam.rqrs.dev
  • Monthly credits come with your plan, and you can top up
  • Runs on servers in Europe
How Reqursor Credits work

On your own server

You run it, with your own key.

Install it on a Linux server or a Raspberry Pi 5, with or without Docker. Connect your own Anthropic API key: your provider bills you directly, and requests go straight to it, never through Reqursor.

  • One command installs it on Linux
  • Code and tickets go only to your AI provider, your git host and the tools you connect
  • Reqursor gets a daily license check, never your code
See the install options

Either way

You set what it may spend.

Cap what each project spends per ticket, per day and per month. When a cap is reached, the ticket pauses with its work kept, and carries on when you approve more.

Compare plans and prices

FAQ

No. Technical teams hand it tickets from GitHub, GitLab, Jira or Linear and get checked draft code changes back. Anyone else can use the AI chat: describe what you want in plain words, check the draft ticket or the preview it shows you, and confirm. Changing online stores through the chat is in early access.

Any code project whose build and tests run from a command, on GitHub (github.com) or GitLab, including GitLab you run yourself. Setup proposes the commands for Node.js, Python, PHP, Go, Rust, Maven and Gradle projects. In early access it also changes how an online store that Reqursor runs for you looks, starting with its colors and design settings.

Yes, by default. A code change waits as a draft on its own branch, and your team reviews it before anyone merges it. For an online store, in early access, you compare a before and after preview of your own page, and nothing is applied until you press Confirm and apply.

In an online store, it never changes your products, prices, coupons, orders or customers, and it does not read your orders or customers. In your code, it does not push to your main branch or merge by itself unless you switch that on, and it refuses force pushes, history rewrites and changes to protected branches.

Choose Start with credits on the pricing page: you buy a starter amount of Reqursor Credits, need no API key, and Reqursor emails you your dashboard address when it is ready. The starter license lasts 14 days, or until the credits are used. Online stores are early access by invitation, so ask us for one.

A code change you no longer want is undone with Revert, which adds a revert commit instead of rewriting history. For an online store, in early access, you can put the store back to an earlier version of the settings Reqursor manages, from the store page, and your orders, customers and products stay as they are.

Still have a question? Get in touch, or read the full FAQ.

Ask for the change. Approve the result.

Hand Reqursor a ticket, or describe what you want in the AI chat. Every change is checked first and waits for your yes.

Contact salesStart with credits

Start with credits runs for 14 days and needs no API key. Changing online stores through the chat is in early access: ask for an invitation.