Support
Fluyo is maintained by one person. That shapes both the right channel to reach it and what you can expect from it. Versión en español.
Before writing
The documentation reads end to end in one sitting and covers the editor, the .fluyo.json format and the MCP server. If your question is "how do I do X?", it is very likely in there.
Where to write
| If your matter is… | Write to… |
|---|---|
| A bug or a feature request for the editor | fluyo issues |
| A bug or a feature request for the MCP server | fluyo-mcp issues |
| An idea you are not going to implement right now | ideas.md, via issue or pull request |
| Privacy, data or legal matters | Email (below) |
| A security vulnerability | Email, privately. Do not open a public issue |
| Anything else |
Public issues are the preferred channel for bugs and improvements. It is not about offloading work: in an issue the conversation stays archived, the next person who hits the same thing finds it, and anyone can contribute. An email is read by two people only.
Support email
Write in English or Spanish, whichever suits you.
Response time
Fluyo is a free, MIT-licensed project maintained in spare time and without a service level agreement. That said, the realistic commitment is this:
| Type of matter | First response |
|---|---|
| Privacy, data or legal matters | Within 72 hours |
| Security vulnerability | Within 72 hours |
| Everything else — bugs, usage questions, MCP server down | Within a week |
| Feature requests and ideas | No deadline. All of them get read |
"First response" means someone has read your message and replied, not that the problem is solved. A reproducible bug is usually fixed quickly; one that cannot be reproduced may stay open for a long time.
How to write a good report
What speeds up a fix the most, in order:
- The
.fluyo.jsonfile it fails with, if you can share it. It is the only thing that allows the problem to be reproduced exactly. If the diagram is confidential, a minimal example that fails the same way works perfectly. - What you expected and what happened. "The GIF jumps when it loops" says far more than "export is not working properly".
- Browser and operating system. Several editor features — the eyedropper, the clipboard, fullscreen — depend on APIs that are not in every browser.
- Console errors, if you know how to open it (F12).
- For the MCP server: which client you use and whether you go through the remote connector or locally over stdio.
Security
If you find a vulnerability, write to the address above privately and allow a reasonable period for it to be fixed before disclosing it. The full policy is in SECURITY.md.
Contributing
Pull requests are welcome and require installing nothing: the editor is HTML, CSS and JavaScript with no dependencies and no build step. CONTRIBUTING.md explains the structure and includes step-by-step guides for adding an icon and an animation.
For small fixes, send the pull request directly. For large changes, open an issue first: agreeing on the approach is faster than redoing the work.
If you need more than this project can give
If you depend on Fluyo for something critical and need availability guarantees or committed response times, the honest answer is that this service cannot give them to you. What you can do, without asking anyone's permission:
- Host your own editor. They are static files: any server will do.
- Deploy your own instance of the MCP server, without the limits of the public endpoint.
- Run the MCP server locally over stdio, with no network in between and no caps at all.
Everything is MIT-licensed and documented in the repositories. That is the concrete advantage of the project being free software.