Coming soon

Configure the agents that run your workflows.

Build workflows where you decide the steps, agents that choose their own, or both. Run them from Marvin Console, see every result before it goes anywhere, and keep a record of every step, including the ones an agent chose.

Join the waitlist See how it will work

claims-intake, version 4Succeeded

GuidedExtract the claimModel call, output checked against a schema
FixedLook up the policyHTTP tool: policy-lookup
BoundedTriage the claimAgent with 3 tools, at most 8 calls
PersonApprove refunds over $500Approved by a claims manager
GuidedDraft the replyModel call with the customer's own key

An illustrative run. Every step, input and decision is kept in the audit trail.

Workflows, agents and runs

Three ideas, and everything in Marvin builds on them.

Workflow: You decide the steps: their order, conditions and where people step in. The same input always takes the same path.
Agent: You set a goal, the tools it may use and its limits; the agent decides each next step. Put agents inside workflows wherever judgment helps.
Run: One execution of a workflow or an agent. Every run leaves a record that cannot be edited, with every step, including the ones an agent chose.

What an agent did, and why

1Read the customer's emailConfiguredTrigger: new email to support@
2Look up order 88213Agent choseWhy: the email mentions a late delivery for this order
3Check the shipping statusAgent choseWhy: the order shows shipped 9 days ago, past the promised 5
4Draft an apology with a voucherAgent choseWhy: policy allows a 10% voucher after 7 days' delay
5Review before sendingPersonWaiting for the support team

An illustrative run. Each step also records its inputs, outputs, model, cost and time.

The result, before it goes anywhere

How much freedom each step gets

Inside a workflow, you choose each step's mode. Keep what must never change fixed, and let agents work only where judgment helps.

Fixed

Deterministic steps: transforms, checks and API calls.

Integrations, data clean-up

Guided

A model call whose output must match a schema.

Extraction, classification, drafting

Bounded

An agent picks tools within call limits, budgets and approvals.

Research, triage, reconciliation

Open

An agent with a goal, tools and guardrails, in a conversation.

Assistants for staff and customers

People in the loop, built in

Any step, whether you configured it or an agent chose it, can hand work to a person. The run waits, for minutes or weeks, and continues with their answer.

Approve: Approve or reject with a comment, above an amount or before anything is sent, paid or changed.
Review and edit: See the result as it will be delivered, change it, then send it on.
Answer: When an agent is stuck or unsure, it asks a person instead of guessing.
Spot-check: Rate a sample of finished results to keep quality visible over time.
Take over: Step in and finish a step by hand; the run continues with your result.
Assigned, on time, on record: Tasks go to a person, role or team with a due time, reminders and escalation, in the Console or by email, and every response is recorded.

How it will work

Business teams and developers work on the same workflows, and nothing reaches production until it passes its tests.

Connect
Use Marvin Gateway or add your own model keys, and connect the systems your work lives in: APIs, MCP servers, email and apps.
Build
Start from a template, describe the work in plain words, or build it visually in Studio. Developers can use code and Git.
Preview
Try a draft on real examples, compare it with the live version, and activate it once its evaluations pass.
Run and export
Start runs from the Console, the API, a schedule, a webhook or an email. Approve where you asked to, and export the results.

Everything runs in Marvin Console

One web app for everyone involved: builders configure, operators run, approvers decide, and clients see their own work, each in their own workspace.

Run on demandStart any workflow from a simple form, attach files, and watch each step as it happens.
Preview before it goes liveTry changes on real examples and compare them with the live version, with no emails or payments sent.
Export anythingResults, run lists, audit trails and configuration, as PDF, Word, CSV or JSON.
One inbox for peopleApprovals, reviews and agents' questions in one place, with the context to act, whichever workflow or agent asked.

See what the Console does

Built to run real work, not demos

The parts teams usually build themselves after the first prototype will be there from day one.

Runs that finish: Each step is saved as it completes, so a timeout, outage or deploy resumes the run instead of losing finished work.
People where you choose: Approve, review, answer or take over at any step. A run can wait days for a person without holding anything up.
A record of everything: Inputs, outputs, versions, costs and decisions are kept in an audit trail you can search and export.
Budgets per client: Set token and spending limits per workspace, so runs stop before they overspend.
Models your way: Use Marvin Gateway, with models from major providers and no keys to manage, or connect your own Anthropic, OpenAI or Google keys and pay providers directly.
One workspace per client: Each client's data, keys and configuration stay separate, which is what agencies need.

Connects to what you already use

Marvin reaches your models, systems and channels through open standards first, with ready-made connections for common apps to follow. All connection types.

Models: Through Marvin Gateway with no keys to manage, or with your own keys for Anthropic, OpenAI, Google and other providers. Choose the model per step.
Tools: Any HTTP API and any MCP server, so agents can read from and act in your own systems. Ready-made connections for apps such as Google Drive and Microsoft 365 are planned.
Starting runs: The API and TypeScript SDK, schedules, webhooks from other systems, and incoming email.
Where people work: Marvin Console and email at launch, on a phone or a desk; Slack and a chat widget are planned.

Built for everyone, with or without code

Business teams and developers work on the same workflows, each in the way that suits them.

No code needed

Start from a templateReady-made workflows for common work, adjusted to your team.
Describe it in plain languageMarvin drafts the workflow for you to review and change.
Build visuallySteps, people, tools and conditions in one editor.

Code when you want it

A code view in StudioEvery workflow is readable configuration you can edit directly.
Git and the marvin CLIKeep workflows in your repository, review changes and deploy them.
API and TypeScript SDKStart runs, read results and answer tasks from your own systems.

See the developer quickstart

Who Marvin is for

Teams that know their work and want it done reliably, without building the platform themselves.

Agencies building agents for clients

Run every client in its own workspace with its own model access, budgets and audit trail, bill model usage through Marvin credits if you like, and reuse your best workflows across clients.

Operations teams with document-heavy work

Hand over customer emails, invoices, contracts or weekly reports without waiting for an engineering backlog, and keep people in charge of the decisions that matter. See use cases.

Join the waitlist

We are opening Marvin to a small group of early users first. Tell us about the work you would like it to do, and we will be in touch when there is a place for you. How early access works.

We use your details only to manage the waitlist and contact you about Marvin. See our privacy policy.

Questions

About Marvin, early access and how we work.

About Marvin

What is Marvin, in one sentence?

A platform where you configure workflows, prompts, tools and rules, and get AI agents that run that work reliably, with approvals and an audit trail.

What is the difference between a workflow and an agent?

In a workflow, you decide the steps. An agent gets a goal, tools and limits, and decides each next step itself. Most processes combine both: a workflow with agent steps where judgment helps.

Where do my team and I use Marvin?

In Marvin Console, a web app with nothing to install. You configure, preview, run, approve and export there. Developers can do the same through the API and TypeScript SDK.

Do I need to write code?

No. Start from a template, describe the work in plain language for Marvin to draft, or build it in the visual editor. Developers can use the code view, Git, the API and the TypeScript SDK on the same workflows.

Who makes Marvin?

Marvin is made by Supawise, an AI and digital transformation company from Vietnam, founded in early 2026.

Results, records and control

Can I see and check results before they are sent?

Yes. Results appear as they will be delivered, such as a formatted document or an email, and any step that sends or changes something can wait for a person to edit, approve or reject it.

Can I audit what an agent did?

Yes. Every run keeps a record that cannot be edited, with each step the agent chose, the reason it gave, its inputs and outputs, tool calls, model and cost, and every approval. You can replay it step by step or export it.

How do people stay in control?

Any step can hand work to a person: approve, review and edit, answer a question, spot-check results or take over. Tasks are assigned with due times, reminders and escalation, and the run waits until someone responds.

Can an agent ask a person for help?

Yes. When an agent is stuck or unsure, it asks a person in the inbox instead of guessing, then continues with their answer. The question and answer are kept in the run record.

Can I try changes without affecting live work?

Yes. Changes start as drafts that you preview on real examples and compare with the live version. During previews, tools that would send emails, payments or record changes do not.

Can I export my results and data?

Yes. Export results as PDF, Word, Markdown or JSON, run lists and audit trails as CSV or JSON, and your configuration as files. You can also schedule exports or export a whole workspace.

Models, connections and data

Which AI models can I use?

Models from major providers, including Anthropic, OpenAI and Google, in two ways. Use Marvin Gateway, with no keys to manage and usage paid from Marvin credits, or connect your own keys and pay providers directly. You can mix both, and each step can use a different model.

What is Marvin Gateway?

Marvin's built-in access to AI models. Pick a model and run, with no provider accounts or keys to set up. Usage comes from prepaid Marvin credits at provider prices plus a small margin, with spending limits per workspace. It runs on Cloudflare's AI Gateway.

Which systems can Marvin connect to?

Any HTTP API and MCP server, email and webhooks at launch, with ready-made connections for apps such as Google Drive, Microsoft 365, HubSpot and Slack planned. See Marvin Console.

Will my data be used to train AI models?

No. Supawise does not train AI models. With your own keys, data goes to your providers under your account and their terms. With Marvin Gateway, it goes under Supawise's agreements, and we only offer providers whose API terms exclude training on customer data. See Responsible AI.

Where will my data be stored?

Marvin runs on Cloudflare. Each workspace's data is kept separately, and prompts go only to the model providers you choose. See Security and data.

For developers

Is there an API and SDK?

Yes. A REST API described in OpenAPI and a typed TypeScript SDK at launch, with Python to follow. See Developers.

Can I test without real data or charges?

Yes. Test keys use test models and safe tool behavior, with no charges, and marvin dev runs workflows on your own machine.

Can I keep workflows in Git?

Yes. Every workflow is versioned configuration you can pull, review and apply with the marvin command line tool, and test in CI.

Teams and clients

Can agencies use Marvin for their clients?

Yes. Each client gets its own workspace with separate data, keys, budgets and audit trail.

Can my clients use Marvin too?

Yes. Each client gets its own workspace, and you can invite their staff to run workflows and approve steps without seeing any other client's work.

Availability and pricing

When will Marvin be available?

Marvin is coming soon. We are opening it to a small group of early users first, then to everyone. Join the waitlist to hear as soon as you can start.

How does early access work?

We invite teams from the waitlist in small groups, help configure their first workflow, and meet regularly for feedback. See Early access.

Can I see a demo?

We show Marvin to people on the waitlist during early access conversations. Join the waitlist and mention that you would like a demo.

How much will it cost?

We will publish pricing before launch. Marvin will charge for the platform and the steps your runs execute. For model usage, you choose: prepaid Marvin credits through Marvin Gateway, or your own keys with no markup, paying providers directly.

Will there be a free plan?

We plan a free plan for trying Marvin on a small scale, alongside paid plans for production use. Details will come with pricing before launch.

Privacy policy

Last updated 8 October 2026

This policy explains how Supawise collects and uses personal data through this website, marvin.supawise.com, and the Marvin waitlist. It will be updated before Marvin launches to cover use of the product.

Who we are

Supawise, based in Ho Chi Minh City, Vietnam, is responsible for your personal data. Contact us at privacy@supawise.com.

What we collect

Waitlist details you give us: name, work email, company, the kind of organization and the workflow you describe.
Messages you send us by email.
Technical data needed to deliver and protect the website, such as IP address, browser type and request time, processed by our hosting provider.

How and why we use it

To manage the waitlist, contact you about early access and launch, and understand demand. Our basis is your consent, which you can withdraw at any time.
To answer your messages. Our basis is our legitimate interest in replying.
To keep the website secure and working. Our basis is our legitimate interest in protecting our services.

We do not sell your personal data, and this website does not use advertising or tracking cookies.

Cookies

This website sets no cookies and uses no advertising or analytics trackers. See the cookie policy.

Who we share it with

We use these service providers, which process data only on our instructions:

Cloudflare, Inc.: website hosting, security and email routing.
Our email service provider: storing, sending and receiving email, including waitlist emails.

We may disclose data if the law requires it. We do not share waitlist details with advertisers or data brokers.

International transfers

Our providers may process data in countries other than yours. Where required, we rely on appropriate safeguards such as standard contractual clauses.

How long we keep it

We keep waitlist details until Marvin launches and for 12 months after our last contact with you, unless you ask us to delete them sooner.

Your rights

Depending on where you live, you can ask to access, correct, delete or export your data, object to or restrict how we use it, and withdraw consent. Email privacy@supawise.com. You may also complain to your data protection authority.

Children

Marvin is for businesses. We do not knowingly collect data from anyone under 16.

Changes

We will post updates here and change the date above. If a change is significant, we will tell people on the waitlist by email.

Terms of use

Last updated 8 October 2026

These terms apply to this website, marvin.supawise.com, and to joining the Marvin waitlist. Separate terms of service will apply when you use Marvin itself.

Who we are

This website is operated by Supawise, based in Ho Chi Minh City, Vietnam. By using it, you agree to these terms.

The waitlist

Joining the waitlist does not guarantee access to Marvin, a launch date or particular features or prices. We may invite people in any order, and may close or change the waitlist.

Early access program

If we invite you to early access, we will ask you to accept separate early access terms covering use of Marvin, confidentiality and feedback. Early versions may change, contain errors or be unavailable at times, and are not intended for workflows where a mistake would cause serious harm without a person's review.

Information on this website

Marvin is not yet available. Descriptions of features, examples and plans show what we intend to build and may change before launch. They are not an offer or a commitment.

Acceptable use

Do not misuse this website: no attempts to gain unauthorized access, disrupt it, scrape it in bulk, or submit false or unlawful information.

Intellectual property

The website's content, the Marvin and Supawise names and logos belong to Supawise. You may share links and short quotations; other use needs our permission.

No warranty

The website is provided as it is. To the extent the law allows, we make no warranties about its accuracy or availability.

Liability

To the extent the law allows, Supawise is not liable for indirect or consequential loss arising from your use of this website. Nothing in these terms limits liability that cannot be limited by law.

Governing law

These terms are governed by the laws of Vietnam, and the competent courts of Ho Chi Minh City, Vietnam have jurisdiction, unless your local consumer law gives you other rights.

Contact

hello@supawise.com

Marvin Console

The web app where your team and your clients configure, preview, run, approve and export, in workspaces that keep each client's work apart. Nothing to install, no servers to run.

What's in the Console

Eight areas, the same for everyone; roles decide what each person can do in them.

Area	What you do there
Home	See runs that need attention, recent results and usage for the workspace.
Run	Start a workflow or an agent from a form built from its inputs, attach files, watch each step live, and see the result as it will be delivered.
Runs	Search past runs and replay any of them step by step, including the steps an agent chose and why.
Inbox	Tasks waiting for you or your team: approvals, reviews, agents' questions and spot-checks, with the context to act.
Studio	Build from a template, by describing the work in plain language, in a visual editor or in code.
Connections	Choose Marvin Gateway or add your own model keys, connect APIs, MCP servers and app accounts, and test them.
Exports	Download results and audit trails, and schedule regular exports.
Settings	Members and roles, budgets, API keys and where the workspace's data is stored.

Preview every change

Your team can improve a workflow without putting live work at risk.

Drafts and live versionsEdits create a draft. The live version keeps running until you activate the draft.
Preview runsRun a draft on sample inputs or on a past run's inputs and see each step's output, cost and time.
Side-by-side comparisonCompare the draft's results with the live version's on the same inputs.
Nothing leaves in previewTools that send emails, payments or record changes use a test endpoint or a recorded response during previews.
Tests before activationA draft goes live only after its tests on your examples pass.

One inbox for people

Everything that needs a person arrives in one place, from any workflow or agent, with the context to act.

Task	What the person does	When it appears
Approve	Approves or rejects, with a comment	Above an amount, or before a write action
Review	Edits the result, then approves or rejects it	Before anything is sent or changed outside Marvin
Answer	Answers a question or adds missing information	When an agent is stuck or unsure
Spot-check	Rates a finished result	For a set share of runs
Take over	Finishes the step by hand	When an agent reaches a limit, or by choice

Tasks are assigned to a person, role or team, with due times, reminders and escalation. Respond in the Console or by email, on a phone or a desk; every response is kept in the run record.

See every result before it goes anywhere

People judge a run by what it produces, so the Console shows results as what they are, while the run happens.

Rendered, not rawDocuments as formatted pages, emails as they will be sent, tables as tables, extracted data as a form, with the raw data one click away.
LiveEach step's output appears as the run progresses, including the steps an agent chose.
Review before sendingSteps that send or change something outside Marvin can wait for a person, who can edit, approve or reject the result. Every edit is recorded.
Side by sideCompare two runs' results, such as a draft version against the live one.
Export from the previewDownload the result as PDF, Word, CSV or JSON, or send it on through a connection.

Every run on record, even when an agent chose the steps

An agent's record is written as it works, so a step it chose is recorded exactly like a configured one, with the reason it gave. Nothing in a run record can be edited afterwards.

For every step	What is recorded
The step	Its order in the run, and whether it was configured or chosen by an agent
Why it ran	The condition that selected it, or the agent's stated reason
Inputs and outputs	In full, with files kept as references
Tool calls	Each request and response, with secrets removed
Model use	Provider, model, tokens, cost and time
People	Approvals, reviews, answers and takeovers: who, when, through which channel, what changed and why
Versions	The exact versions of the workflow, prompts, tools and rules used

Replay any run step by step, compare it with another, rerun it on a new version, or export its record as a PDF for people or as JSON lines for audit systems.

Export your results and your configuration

Your work is yours. Take results, records and configuration wherever you need them.

What	Formats	How
A run's results and documents	PDF, Word, Markdown, JSON	From the run, at any time
Many runs	CSV, JSON lines	From a filtered list of runs or a batch
Audit trail	CSV, JSON lines	Any period, for audits and reviews
Configuration	Versioned JSON files or a bundle	To Git, another workspace or another account
Scheduled exports	Any of the above	Daily, weekly or after each run, by email, webhook or to connected storage
Whole workspace	Archive of configuration, runs and audit trail	On request, including when you leave

Connect your systems

Open standards first, then ready-made connections for common apps. Each connection belongs to one workspace, keeps its secrets encrypted and can reach only what it declares.

Connection	Examples	Availability
Model providers	Marvin Gateway with no keys to manage, or your own keys for Anthropic, OpenAI, Google and others	At launch
HTTP APIs	Any REST API, with an API key or OAuth	At launch
MCP servers	Any remote MCP server, for tools and data	At launch
Email	An inbox address that starts runs; replies and notifications	At launch
Webhooks	Incoming webhooks start runs; outgoing webhooks report results	At launch
App accounts	Google Drive, Microsoft 365, HubSpot, Slack and similar apps	Planned
Databases	Read access to PostgreSQL and MySQL for lookups	Planned

Two ways to use models

Each workspace chooses, and can mix both step by step.

	Marvin Gateway	Your own keys
Setup	None: pick a model and run	Add a key for each provider in Connections
Paying for models	Prepaid Marvin credits, at provider prices plus a small margin	Directly to your providers, with no markup from us
Models	A curated catalog from major providers and open models	Any model your provider accounts can use
Terms	Supawise's agreements; only providers that exclude training on customer data	Your own agreements with each provider
Spending control	Credit limits per workspace	Budgets per workspace, plus your provider's limits
Good for	Getting started, and agencies billing clients through Marvin	Teams with existing provider contracts or high volume

Built for many clients

An account holds workspaces, and each workspace has its own members, roles, connections, budgets and data. Agencies keep one workspace per client and can invite the client's own staff to run and approve their workflows.

Roles that match the work

Viewers see results, operators start runs, approvers decide, builders change workflows, and admins manage members, keys and budgets.

Join the waitlist

Use cases

Everyday work Marvin can take on. Each one combines fixed steps, AI and people, and each will be available as a template you can adjust to the way your team works.

How to read the steps

Fixed: Follows your rules, the same way every time.
Guided: AI reads or writes, checked against the format you expect.
Bounded: An AI agent decides what to look up or do next, within limits.
Person: Someone on your team approves, reviews, answers or decides.

Customer support

Answer customer emails

Today. Your team reads every email, looks up the order and writes a reply, often to the same few questions.

With Marvin. Marvin drafts a reply with the right order details for every email, and your team approves it with one click.

You get: Ready-to-send replies waiting in your inbox.

GuidedRead the email and work out what the customer needs
BoundedLook up the order, delivery or account details
GuidedDraft a reply in your company's tone
PersonApprove, edit or reject before it is sent

Finance

Process invoices and receipts

Today. Invoices arrive as PDFs and photos, and someone types them into the accounting system by hand.

With Marvin. Marvin reads each invoice, checks it against the order and prepares the entry for your accounting system.

You get: Checked entries ready to book, and a short list of what needs a look.

GuidedRead the supplier, amounts and line items
FixedMatch it to the purchase order and delivery
BoundedLook into anything that does not match
PersonApprove unusual amounts before they are booked

Sales

Follow up on new leads

Today. Leads from your website and events wait days for a first reply, and some are never answered.

With Marvin. Marvin researches each new lead, checks it against your criteria and drafts a personal first email.

You get: Every lead answered quickly, with the research attached.

FixedCollect new leads from your forms and CRM
BoundedResearch the company and the person's role
GuidedRate the lead and draft a first email
PersonSend it, or hand the lead to a salesperson

People and hiring

Screen job applications

Today. Recruiters read hundreds of CVs to find the few that match the role.

With Marvin. Marvin summarizes each application against the role's requirements, so recruiters decide faster. People make every hiring decision.

You get: A short, consistent summary for every applicant.

GuidedRead the CV and pick out experience and skills
FixedCheck the role's must-have requirements
GuidedWrite a short summary of strengths and gaps
PersonA recruiter decides who to interview

Legal and operations

Review contracts and documents

Today. Every contract is read line by line to find the few clauses that really matter.

With Marvin. Marvin compares each contract with your standard terms and highlights what is different, with suggested wording.

You get: A summary of the differences and a marked-up copy to export.

GuidedFind the key clauses: dates, payment, liability, renewal
GuidedCompare each one with your standard terms
FixedFlag high-risk differences using your rules
PersonYour lawyer reviews only what was flagged

Management

Prepare weekly reports

Today. Every Monday, someone copies numbers from several systems into a spreadsheet and writes a summary.

With Marvin. Marvin collects the numbers, explains what changed since last week and prepares a report your team can read in minutes.

You get: A finished report, ready to share or export as PDF or Word.

FixedEvery Monday, collect figures from your systems
GuidedCompare them with last week and explain the changes
GuidedWrite the report with tables and highlights
PersonReview it, then send it to the team

Have different work in mind? Join the waitlist and tell us about it.

Developers

Marvin is built for developers as much as for business teams: one small API, a typed SDK and tools that feel native, so your first run takes minutes, not days.

Your first run in four steps

The quickstart we are building for early access. Every step works with a test key, so nothing touches live data or costs credits.

Create a test key
In Marvin Console, create a key that starts with mrv_test_. Test keys use test models and safe tool behavior, with no charges.
Install the SDK
```
$ npm install @supawise/marvin
```

Start a run

Pick a template, such as answering a customer email, and run it with your own input.

import { Marvin } from "@supawise/marvin";

const marvin = new Marvin(process.env.MARVIN_API_KEY); // mrv_test_... while you build

const run = await marvin.runs.create({
  workflow: "answer-customer-email",
  input: { email: inbound },
});

const result = await marvin.runs.wait(run.id); // or listen for run.succeeded
console.log(result.output.reply);

Get the result
Wait for it in code, or receive a signed webhook when the run finishes or a person is needed.

What you get

The details that make an API pleasant to build on, from the first request to production.

One predictable API: Consistent resource names, idempotency keys and cursor pagination everywhere, described in OpenAPI.
A typed SDK: TypeScript for Workers, Node.js, Bun and Deno, with types generated from each workflow's inputs and outputs.
Test mode: Test keys run against test models and test connections, with no charges and data kept apart from live.
A local dev loop: Run workflows on your laptop with marvin dev, and their tests in CI with marvin test.
Webhooks you can trust: Signed events for runs and tasks, a delivery log, one-click redelivery and a helper that verifies signatures.
Errors that help: Every error has a stable code, one sentence saying what to fix, a request ID and a link to its documentation.
Every request traceable: Find any request or run in the Console by its ID, so debugging starts from facts.
Stable versions: The API only changes in ways that do not break you; breaking changes come as a new version, with a year of overlap.
More languagesPlanned: A Python SDK follows the TypeScript one.
For AI coding assistantsPlanned: An MCP server so assistants can create, test and run workflows with you.

Webhooks and the command line

React to runs and tasks in your own systems, and keep workflows in Git like the rest of your code.

Verify a webhook in a Cloudflare Worker

import { verifyWebhook } from "@supawise/marvin/webhooks";

export default {
  async fetch(request, env) {
    const event = await verifyWebhook(request, env.MARVIN_WEBHOOK_SECRET);
    if (event.type === "task.created") {
      // tell your team a decision is waiting
    }
    return new Response("ok");
  },
};

Build, test and publish from your terminal

$ npm install -g @supawise/marvin-cli
$ marvin login
$ marvin init my-workflows --template answer-customer-email
$ marvin dev     # run locally with recorded models
$ marvin test    # run the workflow's tests, CI-friendly
$ marvin apply   # publish to your workspace

The SDK, CLI and full documentation open with early access. Join the waitlist to get them first.

Configure the agents that run your workflows.

Workflows, agents and runs

What an agent did, and why

The result, before it goes anywhere

How much freedom each step gets

Fixed

Guided

Bounded

Open

People in the loop, built in

How it will work

Connect

Build

Preview

Run and export

Everything runs in Marvin Console

Built to run real work, not demos

Connects to what you already use

Built for everyone, with or without code

No code needed

Code when you want it

Who Marvin is for

Agencies building agents for clients

Operations teams with document-heavy work

Join the waitlist

Security and data

Separate by design

Your model access

Encryption

An audit trail you can export

People in charge

Least access

Data location

Reporting a vulnerability

Responsible use

Questions

About Marvin

Results, records and control

Models, connections and data

For developers

Teams and clients

Availability and pricing

Privacy policy

Who we are

What we collect

How and why we use it

Cookies

Who we share it with

International transfers

How long we keep it

Your rights

Children

Changes

Terms of use

Who we are

The waitlist

Early access program

Information on this website

Acceptable use

Intellectual property

No warranty

Liability

Governing law

Contact

Marvin Console

What's in the Console

Preview every change

One inbox for people

See every result before it goes anywhere

Every run on record, even when an agent chose the steps

Export your results and your configuration

Connect your systems

Two ways to use models

Built for many clients

Roles that match the work

Use cases

How to read the steps

Answer customer emails

Process invoices and receipts

Follow up on new leads