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.
Keep a shared project background, a clear work scope and control of what gets shared.
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.
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.
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
Upload the revised document to compare it with the previous one. See which blocks need review and the source text behind them.
Review what was added, changed or removed, then confirm the content to share with your AI.
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.
Not a blueprint you use once. A shared reference to return to as work and changes continue.
Describe an idea, or bring documents, meeting notes, chat logs and GitHub materials. An existing project starts from the structure already there.
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.
Connect supported AI tools through MCP, or copy the work request into another tool. Each connection keeps its own delivery and submission records.
Choose what to build and include its background and acceptance criteria in a work request. Start the actual execution in your connected AI tool.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Where it lands depends on your role and scale.
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.
Every role needs a different slice of context. Review the role-scoped context sent to AI and inspect the project change record.
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.
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 →
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.
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.
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 →
Start free without a card, and move up when the team grows.
Building on your own — DroFi for Vibe Coding → · Evaluating it for an organization — DroFi for Business →