Beta — free while we test it

Don't hire an assistant. Hire a company.

Tell it what you need in your own words. A small team of AI helpers plans it, builds it and checks it — on your computer, on the AI account you already pay for.

Ask for the beta See what people make with it

Free during the beta. No card, no sign-up fee.

⬡  MONOPRISE
WHO IS DOING WHAT
📋Planner Waiting
⌨️Builder Waiting
🔍Reviewer Waiting
“Take these three sales files and give me one clean monthly summary.”
● Plan — 4 steps, 6 files
● Read — your three files, 4,812 rows
● Write — 3 files, into a copy
● Run — tried it on the real files, no errors
● Check — read it again, sent one part back, then passed
Ready for you to look at. Nothing has changed yet.

Sound familiar?

You ask for one thing. You get half of it.

Chat-style AI is good at answering. It is much worse at finishing — and that gap is where your afternoon goes.

01

Half the job goes missing

You list five things. It does two, and says it is done. You only notice the other three when you go looking.

02

Nobody checks the work

The same AI that wrote it also grades it, and it always gives itself a pass. You find out it was wrong much later.

03

Your files change first

Some tools edit your folder while you are still reading. If something breaks after that, finding it is your problem.

What you can do

Six things people actually ask it for.

None of these need you to write a line of code. You describe the job, you read what came back, and you decide whether to keep it.

SPREADSHEETS

“Every month I get three sales files from three branches. Merge them, drop the duplicate rows, and give me one sheet with a total per product.”

WHAT COMES BACK

  • A small program that does the whole thing in one click, so next month you just drop the new files in.
  • It runs the program on your real files while you watch, and shows you the sheet it produced.
  • A short note in plain words: how many rows it read, how many it threw out, and why.

You still have to open the result and check a few rows yourself. It does the boring part, not the trusting part.

A SMALL INTERNAL TOOL

“Our team books meeting rooms in a group chat and it is a mess. Make a simple page where you pick a room and a time, and it lists who booked what.”

WHAT COMES BACK

  • A working page you can open in a browser on your own machine and click through.
  • Fixes while you talk: “make the date bigger”, “stop people booking the same slot twice”.
  • Instructions for the one step you have to do yourself — putting it somewhere your colleagues can reach.

Good for a tool your own team uses. Anything customers touch needs a developer to look it over first.

TIDYING UP FILES

“This folder has 2,000 photos with names like IMG_0423. Rename them by the date they were taken and sort them into folders by month.”

WHAT COMES BACK

  • A list of the first twenty renames, so you can see the pattern before anything moves.
  • Nothing is touched until you say go, and there is a point to roll back to afterwards.
  • The same job saved, so you can run it again on next month's folder.

Keep a backup of anything irreplaceable anyway. That is true of every tool, not only this one.

THE UNFINISHED PROJECT

“I started this eight months ago and forgot how it works. Read it, tell me where I stopped, and finish the sign-up screen.”

WHAT COMES BACK

  • A summary of what the project already does, written for someone who has forgotten everything.
  • A list of what is missing, in the order it should be done, which you can edit before it starts.
  • Then the work itself, one piece at a time, each one shown to you before it lands.

This is where it shines. Picking up cold work is exactly the part people never get back to.

CODE SOMEONE ELSE WROTE

“A contractor left us this. Explain what it does in normal words, then change the company name and the logo everywhere it appears.”

WHAT COMES BACK

  • A walkthrough of the parts that matter, with the file names, so you know where things live.
  • Every place that needs changing, found for you — including the ones you would have missed.
  • The changes side by side, old on the left and new on the right, for you to approve one by one.

It reads it all from your own disk — and the one doing the reading is the AI account you connected, not a server of ours.

THE WEEKLY REPORT

“Every Monday I copy numbers out of four files into the same slide deck. Do that for me and leave the layout alone.”

WHAT COMES BACK

  • A program that fills in this week's numbers and leaves everything else exactly as it was.
  • A test run on last week's files, so you can compare its output against what you made by hand.
  • A shortcut you double-click on Monday morning.

Best when the files arrive in the same shape every week. If the shape keeps changing, so will the fixing.

And what it is not. This is not “an app on the App Store by tonight”. What it is good at is the small, repetitive, annoying work that sits between you and going home — the kind nobody has time to build properly.

A job like the ones above usually takes anywhere from ten minutes to an afternoon, and part of that time is you reading and saying yes.

How it works

Three steps. That's the whole thing.

STEP 01

Say what you want

Type it the way you would say it to a colleague. There is no special wording to learn and nothing to set up first.

STEP 02

The team splits it up

One helper decides the order, one does the work, and a third one checks it and sends it back if it falls short.

STEP 03

You look, then approve

You see exactly what will change, in full, before it happens. Approve it or throw it away — both take one click.

⬡  MONOPRISE
WHO IS DOING WHAT
📋Planner —
⌨️Builder —
🔍Reviewer —

The team

Three helpers. One job each.

They are not three chat windows. They hand work to each other, and the last one is allowed to reject the work of the one before it.

01

Planner

Turns one sentence from you into a list of steps in the right order, and says which files it expects to touch. You can rewrite that list, or cut it down, before anything starts.

Plan · 4 steps · 6 files to touch
02

Builder

Actually opens the files, writes the change and runs it to see whether it works. Everything it writes goes into a copy, so your own files sit untouched the whole time.

Changed 3 files · ran it · no errors
03

Reviewer

Reads the finished work against what you originally asked for. If a piece is missing it goes back to the Builder, and you never see that round trip.

Read 3 files · sent 1 back · passed on the retry

Why bother splitting it up? Because one AI marking its own homework is the reason you get half a job. Here the checking is done by a different helper, with your original request in hand and no attachment to the work.

The honest answer

“Do I need to know any of this?”

You do not have to write anything. But you cannot walk away either — somebody has to look at the result and say yes, and that somebody is you.

YOUR PART

  • Say what you want clearly enough that a new colleague could act on it.
  • Open the result and try it — does the number look right, does the page do what you meant?
  • Press approve, or throw it away and say what was wrong.
  • Decide what matters. It has no idea which mistakes you can live with and which ones you cannot.

ITS PART

  • Break the request into steps and put them in a sensible order.
  • Read your existing files first, so the change fits what is already there.
  • Write it, run it, and try again when it fails.
  • Explain what changed in plain sentences, before you approve it.

So: no, it is not fully automatic. Anyone telling you their AI works with nobody watching is selling you something. The useful question is not “can I stop paying attention” — it is “how little attention does this need”. Here, it needs you at the start and at the end, and not much in between.

If you have never opened a code editor in your life, that is fine. Start with the chat-style app further down this page.

Safety

Nothing changes until you say yes.

Every change is written into a copy first. Your own files sit exactly as you left them until the moment you press approve.

👁️

You see it first

The old version and the new one, line by line, with the changed parts marked. Nothing is summarised away.

↩️

A point to go back to

Right before anything is applied, the state of your folder is saved. One click puts it all back the way it was.

🎚️

You decide how often it asks

Five settings, from asking before every single move to working through a long job while you are somewhere else.

sales_report.py — about to change
- rows = read_file("march.csv")
+ rows = read_all(["march.csv", "april.csv", "may.csv"])
+ rows = drop_duplicates(rows, key="order_id")
Approve Throw away Until you press one of these, the file on your disk has not changed.

The five settings, in plain words

1 · Ask me anything It checks with you before nearly every move. Slow on purpose — use it the first day, or on a folder you are nervous about.
2 · Ask before every change Reading is free. Anything that writes, deletes or runs a command waits for your yes.
3 · Normal (default) Ordinary edits go ahead on their own. Anything that looks risky still stops and asks. This is where most people stay.
4 · Don't interrupt me It works straight through without asking — and the genuinely destructive commands are refused outright instead of being put to you.
5 · Leave it running For a long job you start and walk away from. Nothing is put to you at all, so keep it to folders where a mistake is survivable — the three blocks below still hold.

Three things are blocked at every setting. It cannot reach outside the folder you opened. It cannot edit or delete the file that holds its own rules. And anything you have written down as forbidden stays forbidden, right up to the most hands-off setting. Those three are not a preference you can switch off.

One exception, said out loud. If you connect a subscription like Claude Code instead of a key, that company's own program does the editing, in its own window — so on that route there is no preview before the change, only the roll-back point afterwards. The app tells you this every single time before it starts.

Your machine, your files

It runs on your computer.

Your files are read and written on your own disk. They are never uploaded to us, because there is no server of ours for them to pass through — we never built one.

💻

Your files stay put

The only thing that leaves your machine is the request itself, plus the parts of the file it needs to read — and that goes straight to the AI company you chose, not to us.

🏢

Work files

Because nothing passes through us, the only question left is your own company's rule about sending anything to an outside AI service. Ask before you point it at work material.

📶

You do need the internet

The thinking happens at the AI company, so you need a connection — unless you run a model on your own machine, which it also supports.

The money

You already pay for the AI. We don't resell it.

Monoprise is the app around the AI, not the AI itself. You bring the account. Nothing you spend on it comes to us, and we take no cut of it.

🎫

A plan you already have

If you pay monthly for Claude Code, OpenAI Codex or Google Antigravity, sign in once and keep using the plan you already buy. Nothing extra to pay.

🔑

Or pay for what you use

Paste a key from Anthropic, OpenAI, Google or Groq and they bill you directly, by usage. There is no plan to buy, and you can stop any time.

🏷️

What we charge, today

Nothing. The beta is free, and there is no card to enter. We will charge for the app itself one day, and we will say so clearly before we do.

Claude · ChatGPT · Gemini · Groq Or a model running on your own computer, which costs nothing per use No markup, no middleman fee

One caution, so it does not surprise you. If you pay by usage rather than by plan, a team of three helpers reads and writes more than a single chat window does, so it costs more per job. The app shows you the running cost, and you can cap it or switch to a cheaper model for the routine parts.

Two apps

Which one is for you?

They do the same work with the same team and the same approval step. The only difference is how much of the machinery you see.

IF YOU'RE NEW TO THIS

Monoprise Chat

★ Start here if you don't write code

One window that looks like any messaging app. You say what you want, and what comes back is written in normal sentences, not code you have to decipher.

Nothing to configure — open it, pick a folder, start typing
It tells you what it changed, in plain words
You can still see the exact change before approving, if you want to
Same team and same safety rules as the other app
IF YOU WANT THE CODE IN FRONT OF YOU

Monoprise IDE

A full code editor with the team living in a side panel. If you already use VS Code, this is that, with your settings and extensions still in place.

Built on VS Code, so everything you know still works
Watch each file being changed as it happens
Approve or discard each change one at a time
Runs your project, your tests and your terminal in place

You can switch later without losing anything. Both apps share the same settings and the same AI accounts on your machine.

Where we are

It's a beta. Here's the honest version.

We haven't launched. Below is what works today and what doesn't, with nothing quietly left out.

WORKS TODAY
Both apps run on Windows
Your own key, or a plan you already pay for
Planner, Builder and Reviewer working in order
Preview, approve, and a point to roll back to
Five settings, with the dangerous things blocked in all of them
See the tokens each connection has spent — and set a cap
NOT YET
No download page — we email you the build
Windows only. No Mac or Linux version yet
No paid plans, no accounts, no team features
Gemini works with a key, but not with a Gemini subscription
The apps are in Korean only — five languages is this site, not the app
Long jobs can still get stuck and need you to step in

And the plain truth: it still gets things wrong. It misreads what you meant, it takes a longer route than a person would, and sometimes it is simply confident and mistaken. That is exactly why nothing is applied without you looking at it first.

Questions

Plain answers.

Do I really not need to know how to code?

You never have to write any. But you do have to read what came back and decide whether it is right — nobody else can do that for you. If you have never opened a code editor, use Monoprise Chat and you will not have to see any code at all.

How do I install it?

Leave your email at the bottom of this page and we send you the build within a day. You unzip it and double-click. It does not need admin rights and it does not install itself into Windows, so deleting the folder removes it completely.

What does it cost?

The app is free during the beta and there is no card to enter. What you pay for is the AI itself, and you pay that to the AI company, not to us — either through a plan you already have or by usage on your own key. We add nothing on top.

Where do my files go? Do you see them?

They stay on your disk and we never see them. There is no Monoprise server in the path — we never built one. What does leave your machine is your request and the parts of your files the AI needs to read, and that goes directly to the AI company you chose, under their terms.

Can I use it on work material?

Technically yes, since nothing passes through us. The real question is your employer's policy on sending anything to an outside AI service, which is the same question as using ChatGPT at work. If your company runs its own model in-house, you can point Monoprise at that instead, and then nothing leaves the building.

Do I need the internet?

Yes, for the AI part — the thinking happens at the AI company's end. The only exception is a model running on your own computer, which works with no connection at all but needs a fairly powerful machine.

What if it breaks something?

Changes are written into a copy first, so until you approve, your own files have not been touched. And right before anything is applied, the state of your folder is saved, so one click puts it all back. Keep a backup of anything irreplaceable anyway.

What kind of thing is it bad at?

Anything vague. “Make it better” gets you nothing useful. It is also weak on work that depends on knowledge only you have — your company's rules, why a file is shaped the way it is, which of two correct answers your boss wants. And it is not the tool for building something big that customers will pay for.

How long does a job take?

A small tidy-up job is minutes. Something like the monthly report example can take an afternoon, mostly because you will go back and forth a few times before it is right. It is not instant, and anyone promising instant is not counting the part where you check the result.

Which app should I pick?

If you do not write code, Monoprise Chat. It is one window, it explains itself in normal sentences, and you never have to look at code unless you ask to. Pick Monoprise IDE if you already use VS Code and want the team next to your editor.

Can I stop it in the middle?

Yes. There is a stop button, and it stops the whole team, not just the sentence being written. Whatever had already been written into the copy is still there for you to look at, approve or discard.

What happens to my key, or my sign-in?

It is kept on your own machine and used to talk to the AI company directly. It is never sent to us, and it is hidden from the logs the app keeps. If you signed in with a plan instead of a key, that sign-in stays where the AI company's own tool put it.

Something we didn't answer? The developer page goes into the machinery →

Want to try it?

Leave your email and we'll send you the build within a day. Tell us what you're hoping to make and we'll write back about whether it's a fit.

Which one should we send?

Not sure? Take Chat — you can switch later and lose nothing.

Beta · free · no card

Prefer to just email us? monoprise@monoprise.dev

Used only to send you the beta build. No newsletter, nobody else sees it.