Frequently asked questions

Two products that take on real engineering work: Reqursor Platform and Reqursor Development. Every change they make is validated, checked and traceable before it ships.

In Reqursor Platform, every change is triple-checked before anything goes live, and anything that fails a check is stopped. If a change still causes a problem, you can undo it in one click; orders and customers stay untouched. In Reqursor Development, your own checks run as hard gates: a failing check blocks the change, whatever the AI says.

Maurice Boendermaker and Yassine Abderrazik, the co-founders, based in Rotterdam, The Netherlands.

Reqursor comes from recursion, the favorite computer science concept of our founders. A system that builds new systems, using the same system, was the idea behind it from the start. Read more on our About page.

Reqursor Technologies is a software company based in Rotterdam, The Netherlands.

Use the contact form or email [email protected].

Yes. Reqursor Platform is at platform.reqursor.com and Reqursor Development is at development.reqursor.com. Reqursor Licensing, the license portal for Reqursor Development, is at license.reqursor.com. This site describes the products and links to them.

Reqursor Platform takes over the technical work of agency stores: it moves, runs and builds online stores for ecommerce agencies, around the clock, so every store is secure and ready for AI shopping agents. AI proposes each change, and every change is checked before it goes live, so any change can be undone.

Ecommerce agencies that build and run online stores for their clients.

You can take on more stores without hiring more developers. Reqursor Platform does the technical work of moving, running and building stores, around the clock. You keep the client and the creative decisions: which clients to take on, how each brand should look and what to build next.

Every change moves through the same steps, in order: Describe, Check, Confirm, Save, Plan, Go live, and Keep in sync. You see a preview and confirm before a change reaches a live store.

Every version of a store's setup is kept, so any change can be undone, back to the last version that worked. Orders and customers stay untouched.

Each store runs in its own separate environment, so a problem in one store stays in that store.

Reqursor keeps checking each store against the setup you approved. Changes you ask for wait for your confirmation. Changes nobody asked for are spotted and fixed automatically, back to the setup you approved.

Yes. A live store does not depend on Reqursor Platform's AI or dashboard to keep serving visitors and taking orders, and monitoring and undo keep working on their own. While the AI is unavailable, new drafts, diagnoses and chat pause. Read why in the docs.

No. An undo always goes back to one complete earlier version of a store's setup. If you only need part of an earlier version back, you ask for it as a new change, such as keeping the current homepage copy but bringing back the old color scheme, and you review and confirm it like any other change. Read why in the docs.

Each store shows one of five statuses: healthy, degraded, unexpected change, failing or unknown. The status comes with a summary of how many checks passed, the area affected and how severe the worst issue is. See how store health is checked.

Reqursor Development is an AI development agent. Your developers write the tickets; it implements them in your repository and ships only when your checks pass and every acceptance criterion is backed by evidence. Run it hosted with Reqursor Credits, or self-hosted with your own Anthropic API key or Moonshot AI key (beta).

Software teams that want tickets implemented in their own repository, hosted by Reqursor or on their own Linux server or Windows machine.

Every change moves through the same steps, in order: Ticket, Implement, Checks, Review, Verify, Security scan, and Ship. The agent ships only when your checks pass and every acceptance criterion is backed by evidence.

Every acceptance criterion is linked to the lines of the diff that satisfy it. No evidence, no ship.

Your own build, lint, typecheck and tests run as hard gates. A failing check blocks the change, whatever the AI says.

Run it hosted by Reqursor with Reqursor Credits and nothing to install, or self-hosted on your own Linux server or Windows machine with your own Anthropic API key or Moonshot AI key (beta).

That depends on how you run it. Hosted with Reqursor Credits, you need no API key: model requests pass through Reqursor's inference relay to the model provider. Self-hosted with your own key, Reqursor Development sends model requests straight from your server to the provider you connect, with your own Anthropic API key or your own Moonshot AI key (beta), and never through Reqursor. Moonshot AI needs an opt-in per project, with a data disclosure. Your provider bills you directly.

That depends on how you run it. Hosted with Reqursor Credits, you need neither: Reqursor hosts it, there is nothing to install and your team opens its dashboard in a browser. Self-hosted with your own key, you install it on your own Linux server, with Docker or directly on the server, or on a Windows machine. On Windows the agent runs without the isolation the Linux installs give it, so use a machine you dedicate to it. See the installation page for the requirements.

It has a built-in queue and can import issues from GitHub, GitLab, Jira and Linear. When a ticket that came from GitHub or GitLab ships, the result can be reported back to the original issue. Read about importing tickets.

During setup it inspects your repository and proposes your build, lint, typecheck and test commands from what it finds: package.json scripts for Node.js, JavaScript and TypeScript, and pyproject.toml, composer.json, go.mod, Cargo.toml, pom.xml or build.gradle for Python, PHP, Go, Rust, and Java and Kotlin. Nothing is fixed: you can edit any command or write your own. See how checks are detected.

Yes. A built-in secret scan runs on every ticket and checks the diff against built-in patterns for common credential and token formats. A genuine secret on any changed line blocks shipping, the same way a failing test would. Read about the secret scanner.

Yes. By default each ticket ships on its own branch and opens a draft pull request, so your team can review it before it merges. The agent cannot force-push, rewrite history or push to branches you protect, and approving a run needs an Owner or Admin by default. Read about branches and automation.

Yes. Every project has spending caps per ticket, per day and per month. When a cap is hit, the project stops picking up new tickets automatically until you raise the cap or the period resets, and manual runs on that project are blocked with a message saying which cap was hit. Read about budgets.

Reqursor Platform is in early access: you request access on its site, and early access starts with a pilot, so you can see it run your own stores before you choose a plan. It is piloting with companies in the Netherlands and Austria. Reqursor Development is onboarding founding customers. Each product's site has the next step.

The overview of both products is at reqursor.com/pricing. The prices themselves are on each product's own pricing page: platform.reqursor.com/pricing and development.reqursor.com/pricing. For Reqursor Development the plan price is the same hosted with Reqursor Credits or self-hosted with your own key; the own-key plan includes no credits because your provider bills you for AI usage.

Reqursor Licensing is the customer portal for Reqursor Development licenses. It is where you buy a license, see your licenses and manage billing. Sign in at license.reqursor.com.

Yes, for a self-hosted install: in Reqursor Licensing at license.reqursor.com, where you also see your licenses and installs and manage billing. Hosted with Reqursor Credits, Reqursor runs the server, so there is nothing to move.

Reqursor Platform is documented at docs.reqursor.com/platform, and Reqursor Development at docs.reqursor.com/development.

Both products share one changelog.

The public status page at status.reqursor.com shows how our services are doing.

Fill in the short application form on the early access page with your name, work email, agency name, how many stores you manage and your biggest operational pain point. Applications are reviewed daily, and early access starts with a pilot.

Start with credits. It comes with the version Reqursor hosts: you pick an amount of Reqursor Credits, need no API key and have nothing to install. After you pay, Reqursor prepares your Reqursor Development dashboard and sends you an email with its address when it is ready. The starter license lasts 14 days and includes Team features for up to 3 developers and 3 projects. After 14 days, or when the credits are used up, you choose a plan. Plans are listed on the pricing page. Start with credits runs on Reqursor Credits only, so a self-hosted install does not offer it, and there is no self-serve trial with your own key. To evaluate a self-hosted install, contact us.

Buy on license.reqursor.com. You pick one of two ways to run it, hosted with Reqursor Credits or self-hosted with your own key, then a plan and a billing interval, and pay through Stripe Checkout. Your license key arrives by email. Hosted, Reqursor prepares your dashboard and sends a second email with its address when it is ready. Self-hosted, you install it on your own Linux server or Windows machine with that key. In a dashboard you already have, use its Buy License button: the dashboard Reqursor hosts sells plans on Reqursor Credits, a self-hosted install sells licenses for your own key, and the install that sent you there activates on its own once payment completes. Solo, Starter and Team can be bought either way online; for Enterprise with your own key, contact sales.

A license runs on one or the other: Reqursor Credits, or your own key. To change an existing license, contact us and we make the change for you.

Nothing is deleted. Starting new runs is blocked, but you can still browse tickets, runs and the audit log, export data and download a backup. A ticket that is already running finishes its current stage.

Invoices, payment methods and cancellation are handled in the Stripe customer portal, which you open from your account on license.reqursor.com.

In the EU. Reqursor Platform runs in data centers in Germany (Falkenstein and Nuremberg) and Finland (Helsinki). See GDPR and data hosting for what data we process.

Only the store settings needed for the task. Passwords, API keys, orders, products and customer records are never sent, and each request holds data for one organization only. The privacy policy lists exactly what is sent.

Reqursor Platform sends store settings to its AI provider, Anthropic, through the Claude API, and Anthropic does not train models on API customer data.

That depends on how you run it. Self-hosted with your own key, code and ticket text leave your install only for the model provider you configured, your git remote and the integrations you configured. Model requests go straight from your server to your provider and never through Reqursor, and the credentials you store are encrypted at rest and never sent to Reqursor. The install still contacts the Reqursor license server for activation, a daily heartbeat with documented metadata and update checks, and none of these carries code or ticket text. Hosted with Reqursor Credits, Reqursor hosts your dashboard and the working copy the agent uses, your code still goes to your git remote and the integrations you connect, and model requests pass through Reqursor's inference relay, which does not store them, to the model provider. See the privacy policy for the details.

Yes. In Reqursor Platform you can export your data in standard file formats with the Data Export feature and delete your account and all its data. For your other rights under the GDPR, such as access or correction, email [email protected].

Report it privately to [email protected] and please don't share the details publicly. Include the page, URL or version affected, the steps to reproduce it and the impact you expect, but never live passwords or keys. The security overview has the full details.

Yes. Read the Data Processing Addendum for Reqursor Platform and the Data Processing Agreement for Reqursor Development.

No. The Reqursor Technologies website and the Reqursor Platform website use no analytics or advertising cookies. If you choose a light or dark theme, that preference stays in your browser's local storage and is never sent to us. See the cookie policy.

No. We never sell personal data or share it with advertisers. We use it to reply to you, provide and bill for our products, keep our services secure and send service notices, security alerts and, with your consent, product updates. The privacy policy has the details.

Yes. Organization admins invite team members and give each one a role: Admin, Operator or Viewer. The security overview describes how access is controlled.

Store definitions are kept as long as the organization exists, deployment artifacts for 90 to 365 days depending on type, audit logs for 365 days and AI interaction logs for 30 days. After you delete your account, all data is permanently purged within 30 days of the grace period ending. See the privacy policy.

No. The agent runs in a sandbox that sees only the project's working copy, and it never sees your data directory, your license or your real API keys. Self-hosted with your own key, model calls pass through a local gateway that adds your provider key on the agent's behalf. Hosted with Reqursor Credits, there is no provider key of yours at all: the gateway sends model calls to Reqursor's inference relay. More on the Reqursor Development security page.