Product · in detail

From design to AI work results,
keep building in the same project.

Start with an idea, or bring your existing files and code. Give AI the background for the work, then review submitted results and changes together.

Start free → See the project workflow
What DroFi does

Work from the same project.
Share only what each task needs.

Keep a shared project background, a clear work scope and control of what gets shared.

№ 01 · Same baseline

New projects and work in progress

Shape a new idea or bring in existing documents and code. Keep what you are building and why decisions were made in the same project, ready to share with your connected AIs.

№ 02 · Import · Dispatch

Bring the background for the work

Choose what to make and bring the related documents and decisions with it. Review what is included or left out before sending, then continue the work in your connected AI tool.

№ 03 · Control · Security

What goes out is up to your team

Team guidelines are sent alongside context to each AI, while material marked no-export is left out of context DroFi creates. What went out through DroFi can be checked later.

When project details change

See what changed
and what each AI received.

  1. Check what changed

    Upload the revised document to compare it with the previous one. See which blocks need review and the source text behind them.

  2. Choose what to send

    Review what was added, changed or removed, then confirm the content to share with your AI.

  3. Check what each AI received

    See what you last sent to each connected AI and what is ready to send next: just the changes or the full content.

DroFi does not watch external files in real time or automatically run every AI. “Delivered” does not mean the AI actually used the context.

Actual Korean app UI showing what was last sent to Codex and the changes ready for its next request.
Actual implemented UI · test data · click to enlarge. Numbers illustrate the screen; they are not product savings or evidence of external AI execution. UI shown in Korean.
Project workflow

Keep the design and work results in the same project

Not a blueprint you use once. A shared reference to return to as work and changes continue.

📄 Docs · repos ✏️ Draw it BLUEPRINT Order flow Refund guide
Step 01

Start something new, or bring it in

Describe an idea, or bring documents, meeting notes, chat logs and GitHub materials. An existing project starts from the structure already there.

CANVAS · DRAFT Decision AI suggests TEAM APPROVES
Step 02

Define what to make

Review the overall flow, requirements and important decisions for this task. Building one feature is not a prerequisite for discussing the next part of the design.

PROJECTBlueprint Claude Cursor ChatGPT Gemini CONNECT ONCE · MCP
Step 03

Connect the AI you need

Connect supported AI tools through MCP, or copy the work request into another tool. Each connection keeps its own delivery and submission records.

▶ PICK A TASK Context that fits context for task Your AI LESS RE-PASTING
Step 04

Start building from the design

Choose what to build and include its background and acceptance criteria in a work request. Start the actual execution in your connected AI tool.

DECISION UPDATEDShipping → free Claude✓ ChatGPT✓ Gemini✓ LATEST ON REQUEST
Step 05

Review results and continue with changes

Compare submitted AI results and evidence, then review which changes to adopt. The next MCP request uses the confirmed baseline. External file changes currently need to be imported again.

Features in detail

Manage project flow, AI work and changes together

Canvas

Canvas

Lay out decisions, screens, guidelines and flows as blocks and arrows. Several people can edit at the same time and you see who is looking where, live. AI asks about the branches you left out and sketches the next block as a dashed suggestion. A diagram for people, exact context for AI — one screen does both jobs.

Import

Import

Turn documents, meeting notes, chat logs and selected files from GitHub repos into a draft blueprint. Review its evidence and make corrections where needed. Uploaded documents stay in the document drawer; repository import has analysis limits and is not a backup of the entire repository.

Role Context

Role context · task context

Project context requested through MCP is scoped by recipient role. A task prompt, however, is scoped by the task itself, not by who dispatched it. What went out through DroFi stays on the record.

Guidelines

Team guidelines

Commit conventions, tone of voice, things never to do — set them once at the team level and the same guidelines are sent alongside context to each AI. They remain a shared team asset instead of scattered personal prompts.

Export Control

Export control

Mark material that must not leave as no-export. It is left out when DroFi assembles AI context, rather than removed from a finished prompt afterward.

History

Record

Who exported what, and through which route, can be checked later. Export history also keeps the blocks included at the time and how often the same content was read again.

Usage

Usage

Each member can see their own monthly AI usage and plan limit. When plan tokens run out, they can connect the AI they already pay for and keep working for free. Today, DroFi keeps project delivery history for context routed through it; consolidated organization audit is planned.

Run Flow

Run the flow

The flow you drew becomes the sequence of work, and AI moves through it one step at a time. Each step carries a "how we know it's done" check, and anything AI proposes changing only reaches the blueprint once a person approves it. You can hand off the work and still hold the standard.

WHO IT'S FOR

For teams, and for one

Where it lands depends on your role and scale.

Small teams

A different AI per person, a different "latest" per tool. Each teammate connects their tool to the same project source, and if setup feels like a lot, a single copy-paste gets you started.

Designers · PMs

Every role needs a different slice of context. Review the role-scoped context sent to AI and inspect the project change record.

Developers (on a team)

It's easy to build on stale assumptions when someone else changed a definition. Receive exactly the changes that touch your work and waste less effort.

Non-developers · vibe coders

For people who can't code but want to build with AI — there's a separate track that starts with drawing. DroFi for Vibe Coding →

Solo developers

For those juggling several AIs alone. Keep the baseline in one place and regenerate context from the same project source, reducing explanations repeated from scratch.

For larger organizations

Today you can inspect project-level delivery records for context sent through DroFi. Org-wide auditing, SSO/SAML and self-hosting are planned features now being shaped through pilots; standard-format export is available today.

FAQ

Questions teams ask

Does AI work update the map automatically?
Supported MCP connections can supply reported progress and submitted results. A received result is distinct from a completed human review. Automatic collection of all AI work or external file changes is not available; external file changes currently need to be imported again. Connections that keep work and the map updated without repeated importing are follow-up development.
Must the whole design be finished before starting work?
Review the overall flow, then refine the requirements and important decisions for what you want to make now. The design remains a reference for results and later changes, rather than a document used only before work. User-flow order and development order are different.
Which AI tools does it connect to?
Tools that support MCP connect directly. For tools that do not, you can copy the full context or a task prompt. The project source of truth does not live inside a single AI vendor.
Where is our data stored?
Projects live on DroFi's servers. When DroFi assembles AI context, it uses only the scope the team allowed and leaves marked material out from the start. It does not control someone manually copying material outside DroFi.
Can teammates use different AI tools?
That's the premise DroFi is built on. One person can use Claude, another Cursor, and another ChatGPT. Context delivered through a connection or copy is generated from the same project source, so the team does not have to standardize on a single execution tool.
Aren't CLAUDE.md, AGENTS.md and Cursor Rules enough?
You can keep using your AI tools’ instruction files and rules. DroFi helps when you want to manage project materials, decisions and submitted results across several AIs in one place. Review the background to send before each task and compare the results that come back. Work still runs in your connected AI tools; DroFi does not automatically collect every external conversation or file change.
Context windows keep growing. Why select at all?
Maximum window length and useful length on a particular task are not the same. NoLiMa (ICML 2025) ↗ defines effective length as the longest context that retains 85% of short-context performance. In the authors' updated table ↗, GPT-4.1 claims 1M tokens and measures 16K effective. The condition matters: this is associative retrieval over narrative prose without lexical overlap. It does not say models cannot find a literal function name in code.
How many tokens does it save? Does it make AI more accurate?
We do not promise one savings percentage. In an internal measurement on Aug 21, 2026, same-depth blueprints with 60–120 blocks ranged from about 1.0× (no meaningful reduction) to roughly 21× versus full context, depending on how the blueprint was connected. On tiny, nearly empty blueprints, the task prompt was larger. We have not run an accuracy A/B yet. What we claim today is not “more accurate”; it is that teams can review what was sent and leave marked material out before context is assembled.
How is this different from Notion or Figma?
Notion pages and Figma files remain the source material people read. DroFi does not replace them; it links decisions and relationships into a blueprint people and AI can share. Persistent role context and task prompts are created separately from that blueprint.
Is it usable for non-developers?
Yes. You draw with blocks and arrows and answer the AI's questions in plain language. PMs and designers can pick a task and create a prompt with context for that task. If you're building something on your own, there's a separate vibe coding track →.
How does no-export actually work?
Mark a document or block as no-export and it is left out when DroFi assembles AI context. The sent-block list can be reviewed later in Export history. The record covers routes through DroFi; it cannot stop or record someone manually copying a screen and pasting it elsewhere.
Do we have to rewrite our existing documents?
You do not have to start from scratch. Use your existing materials to build a draft, then review and correct the evidence and relationships. Uploaded documents are retained; repositories are analyzed within the selected scope. Check the import result for omitted scope and warnings.
Can AI change the blueprint on its own?
It can't. Anything AI proposes appears first as a dashed suggestion, and only a person's approval puts it into the blueprint. Hand off the work; the standard stays with you.
Our company blocks ChatGPT. Is DroFi OK to use?
Companies usually block AI because there's no way to see what goes out. That is the exact point DroFi addresses — material marked no-export is left out of AI context from the start, and whatever goes out through DroFi is recorded block by block in delivery history. Data policies of the AI services you connect still follow each service's own terms, so we recommend reviewing with your security owner before rollout.
How accurate are the drafts made from imported material?
We don't promise an accuracy number. Imported material is split into source-verified facts and inferences held for review, and only what a person approves becomes the source of truth. The more concrete your material, the less there is to review.
How does the beta work, and what does it cost?
We're in beta, so we onboard teams in the order they apply. The Starter plan is free with no card (up to 2 editors), and you can move up when the team grows. The table below has every plan.
How long does it take to get going?
Upload existing documents and repositories to draft the blueprint, review only the items that need confirmation, then connect each person's AI tool. Existing execution tools stay in place; actual setup time depends on source volume and review scope.
Pricing

Plans at a glance

Free for up to 2 editors, no card required. Move up when the team grows.

Starter Free Team Popular Pro Enterprise Custom
Price ₩0 / up to 2 editors ₩9,900 / editor · month Custom quote
Editors Up to 2 Up to 10 · viewers free By agreement
Projects 2 5 By agreement
AI tokens (per person · month) 100K (200K for your first 2 weeks) 1M Planned — covered by your company contract
And Canvas for decisions and flows · multiple AI connections · tailored context delivery · relevant-change alerts One key per program · GitHub code import · shared definitions · permissions · activity log Available: project delivery history · Planned: org audit, approval gates, SSO/SAML, self-hosting and DPA

On every plan, free or paid, you can connect your own AI and keep working for free once the tokens run out. Full plan details are on the pricing page →

Get started

Start fresh or keep building.
One project for you and your AIs.

Start free without a card, and move up when the team grows.

Start free → See the whole story on the home page

Building on your own — DroFi for Vibe Coding →  ·  Evaluating it for an organization — DroFi for Business →