Turn your expertise
into AI workflows
you control.

Build workflows visually, connect AI to your data and tools, and review results at the steps you choose. Explore the online sandbox, then talk to us about deploying QMerse on your own infrastructure.

Your expertise. Your AI. Your control.

supplier-comparison  ·  run 214● running 4/6
Working with

“Grid compliance work used to mean weeks of manual assembly just to produce something defensible. QMerse cut that down and kept the audit trail intact.”

Dr Yousef Pipelzadeh — Founder & CEO, Velon Energy

The whole canvas, stop by stop.

Pick a stop to see that part of the app up close, or let the tour play through them.

    1 / 8
    Node palette
    Data and file inputs, agents, Python scripts, flow control (switch, loop, merge), outputs and logs, all drag and drop.
    The QMerse canvas in light mode: the node palette on the left, a toolbar with Code, JSON, Prompts, Variables, API, Evaluate, Run and Debug, and a data-loading flow on the canvas.
    The QMerse canvas in dark mode: five Python script tools feed a Data Loader Agent, a Data Router agent takes the query and a data file, and the result leaves as markdown. The flow library is on the left and model settings on the right.

    Explore online. Deploy on your terms.

    01 · Explore

    Online sandbox

    Explore the visual builder, try example workflows and test your ideas before discussing a deployment. The sandbox is a shared environment with usage and capability limits.

    File uploads
    Up to 5 MB per file
    Python
    The built-in libraries
    Compute
    Shared with other sandbox users
    Models
    US$5 credit for your first two weeks, then your own API key
    02 · Deploy

    On-premises deployment

    Discuss deploying QMerse within your organisation’s infrastructure. Together, we define the model setup, integrations, compute requirements and support needed for your workflows.

    Infrastructure
    Your organisation’s own
    Models
    Supported cloud and local models
    Integrations
    Scoped as part of your proposal
    Support
    Agreed with you

    Your expertise drives the workflow.

    You decide the process, what the AI may do on its own, and where a person reviews before the workflow continues.

    1. 01

      Define the process

      Connect your data, tools, AI agents and Python logic in a visual workflow.

    2. 02

      Inspect the execution

      Review inputs, outputs and tool activity to understand how a result was produced.

    3. 03

      Choose where approval matters

      Configure approval steps so selected actions wait for a person to review them.

    4. 04

      Reuse your expertise

      Save proven workflows and adapt them to the next task, dataset or project.

    In the online sandbox: all four. With an on-premises deployment: the same, running on your infrastructure with your own Python packages, larger files, integrations scoped to your systems, and shared workspaces for your team. Compare the two

    Three kinds of work, built in QMerse.

    Engineering analysis, document review and recurring monitoring: what goes in, what QMerse does, where you review, and what comes out.

    See all use cases
    Engineering analysisDemo

    Critical minerals intelligence agent

    Task & input
    Screen lithium brine wells and deposits from several geological databases.
    QMerse performs
    Queries the databases, compares concentration, depth and location, ranks the opportunities and drives the map.
    You review
    The ranked shortlist on the map, choosing which opportunities to keep.
    Output
    A structured report on the selected opportunities, for preliminary screening.
    Document reviewDemo

    File reader with skills

    Task & input
    A PDF, Excel or Word file, and a question about it.
    QMerse performs
    Extracts information from supported PDF, Excel and Word files with a File Reader agent and its pdf, xlsx and docx skills.
    You review
    The extracted answer against the source document before it is used.
    Output
    The information you asked for, as a named result.
    Recurring monitoringDemo

    Daily vehicle market monitor

    Task & input
    Public vehicle-market listings, collected on a daily schedule.
    QMerse performs
    Structures vehicle and dealer data, maps activity by ZIP code and appends a dated snapshot without duplicating rows.
    You review
    The run history, the dated snapshots and the ZIP map.
    Output
    A growing time series of the market, with a map built from the same run.

    From business process to repeatable workflow.

    QMerse sits between the information your organisation already has and the decisions someone has to make about it. A process done by hand becomes one you can run again, inspect, and hand to someone else.

    1. 01 · Connect

      Start from what you already have.

      Documents, spreadsheets, databases, APIs and business tools. There is no data platform to stand up first.

    2. 02 · Build

      Wire the process on the canvas.

      Extract, analyse, calculate, compare and decide, step by step, with agents, Python and the tools you already run.

    3. 03 · Approve

      Review where you choose.

      Configure approval steps where human review is required. The workflow pauses there and continues once a person approves.

    4. 04 · Deliver

      Get a finished result, then run it again.

      Structured data, reports, comparisons, alerts or processed documents. Reuse a defined process across repeated runs, and review each run’s output.

    The parts you wire together.

    Wire documents, data, models and code together on one canvas, then reuse what works on the next project.

    Visual workflow builder

    Connect reusable components on a canvas and see the whole process at once, instead of reading it out of a script.

    A routing flow on the QMerse canvas: an Orchestrator agent hands each question to a specialist agent such as the CSV Stat Agent and returns one answer.

    Supported models, your key

    Connect supported cloud and local models, such as OpenAI, Anthropic and Azure, with your own API key. We do not mark up inference.

    The QMerse settings panel: one model setting applied to all LLM nodes, and cost estimation per run.

    Python, APIs and your tools

    Drop into Python for logic that must be exact, and call the systems your business already runs on, all in the same workflow.

    Python script nodes read_pdf, read_excel and read_file wired as tools of the Data Loader Agent.

    Templates

    Start from a template that already runs, then save your own and apply it to the next project, dataset or client instead of rebuilding it.

    The EDA Agent, a saved agent on the QMerse canvas: an EDA Router and an EDA Agent with a query and a CSV file input.

    Build it visually. Take the code with you.

    Export compatible workflows as Python for execution outside QMerse, subject to their dependencies. Keep your own model keys and a history of your runs.

    Runtime
    Export compatible workflows as Python and run them yourself
    Portability
    Run the exported code outside QMerse, subject to its dependencies
    Output
    Ship a working application, with charts people can explore
    workflow / supplier-comparisonEXPORT → pipeline.py
    run history kepton-premises deployment on request

    Built for the people who build.

    QMerse is built around a job, not an industry: work that depends on someone’s judgement, turned into a workflow you can run again and inspect step by step.

    Our missionTo empower domain experts to put AI to work while retaining control over their knowledge, processes and decisions.

    Common questions.

    Why use QMerse instead of just ChatGPT or Claude?

    ChatGPT and Claude give you the model. QMerse gives you the system around it: the workflow that combines AI with your data, tools, code, rules and human approvals, so you can reuse a defined process across repeated runs.

    How does QMerse compare to n8n?

    n8n is strong at connecting applications. QMerse is built for workflows where the hard part is the decision: read the data, run the calculation, have agents interpret it, validate the result, and put it in front of a person. n8n can call a QMerse workflow over a webhook.

    Do I need to be an AI developer?

    No. Domain experts, engineers and analysts build workflows from existing components. Technical users can go further with Python, APIs, custom tools and their own models.

    Can someone build it for us?

    Yes. Zapwiser, the team behind QMerse, can identify, design and implement your first production workflow, then hand it over to your team. How the two fit together.

    Explore what you can build with QMerse.

    Try ideas in the online sandbox, then talk to us about deploying QMerse on your own infrastructure.

    Want someone to build it for you?Work with Zapwiser ↗