Platform Overview

A guided tour of the pieces that make up Reqursor Platform (the AI, the preview-and-confirm step, and the part that makes changes safely) and how they work together to build, migrate, and operate a store.

What is Reqursor? covered the pitch: an AI workforce that builds, migrates, and runs online stores from plain language, with every change checked before it goes live. This page is the guided tour: the actual pieces that make that true, and how a request moves through them.

Two ways in, one platform behind both

You reach Reqursor Platform in two places (together, what Core concepts calls Dashboard & Assistant):

The conversational assistant

Your primary way in. Ask it to build a store, request a change, or ask what's happening with a store, in plain language.

The dashboard

Your view of all your stores. See every store's health at a glance, review and confirm proposed changes, and act across many stores at once.

Both use the same AI and the same system for making changes. Whether you ask by chat or click through the dashboard, the result is the same kind of proposal: previewed and confirmed the same way.

What happens after you ask

The AI understands your request

It reads your brief or your change request and works out which parts of the store's description it touches: design, pages, settings, whatever's relevant.

It's checked before you see anything

The draft is checked against a strict rulebook: nothing broken, nothing contradictory, nothing that points to a version that doesn't exist. Invalid drafts are caught here, never on a live store.

You preview and confirm

You see a clear before-and-after. Nothing about a live store changes until you approve it.

Your approval is put on the record

The confirmed draft becomes the store's official, on-the-record description: what the store is now supposed to be. See how the AI drafts your store setup for your approval.

Reqursor Platform makes the change

It works out what will change, makes the change, then checks that the store matches what you approved. See How every change is checked before it goes live.

Behind the scenes: four jobs, for every store

Once a change is on the record, four parts of the platform do the ongoing work:

Making changes

Works out what will change, makes the change, and checks the result, for every recorded change and every store.

Store platform connectors

Translate Reqursor Platform's general instructions into the exact steps your store platform needs. Reqursor Platform supports one store platform today. Supporting another means adding a new connector, not rewriting the AI.

Separate environments

Every store runs in its own separate environment (its own network, storage, and computing power), so one store's problem never affects another.

Monitoring

Watches every store continuously and reports on its health and on any unexpected changes (changes nobody asked for). This is the evidence the AI uses to find problems and suggest fixes.

What's live today

The conversational assistant, the dashboard, the checks before every change, support for one store platform, and a separate environment for each store are the foundation Reqursor Platform runs on today. Support for more store platforms is on the roadmap; adding one does not require changing the AI.