# Flozu

> Map how your systems connect, and watch traffic move through them.

Flozu is a live canvas for mapping how a company's systems connect. Traffic moves along the lines, parts back up or turn traffic away when they run out of room, and you can run scenarios such as Black Friday or a region going down, try fixes, and present the map as a story. Every page below is plain Markdown. [llms-full.txt](https://docs.flozu.app/llms-full.txt) holds them all in one file.

## Getting started

- [What is Flozu?](https://docs.flozu.app/start/introduction.md): Flozu is a canvas for mapping how a company's systems connect, and for showing how traffic moves through them.
- [Quick start](https://docs.flozu.app/start/quick-start.md): Make your first map, connect it, give it some traffic and test it on Black Friday, in about five minutes.
- [A tour of the editor](https://docs.flozu.app/start/tour.md): What each panel, button and tab in the Flozu editor does.
- [Get Flozu](https://docs.flozu.app/start/install.md): Use Flozu in your browser at my.flozu.app, run it from its source on your own computer, or install the Mac app.

## Walkthroughs

- [Will it survive Black Friday?](https://docs.flozu.app/walkthroughs/black-friday.md): Play Black Friday on a shop's checkout, find the part that falls behind first, size the fix and prove it works, in about ten minutes.
- [What if something breaks?](https://docs.flozu.app/walkthroughs/what-if-it-breaks.md): Take a shop's database down, then its whole cloud region, see who notices, and try the fix in a proposal before you change anything.
- [Explain your system to someone new](https://docs.flozu.app/walkthroughs/explain-it.md): Turn a scenario into a story that walks a new starter, a client or your manager through the map one step at a time, then present it or send it as a link.
- [Make the case for a fix](https://docs.flozu.app/walkthroughs/make-the-case.md): Turn a fix into a proposal, prove it with the same failure played before and after, put a price on it, and tell it as a story your team can say yes to.

## Build a map

- [Your maps, projects and folders](https://docs.flozu.app/guides/your-maps.md): Make, find and sort your maps into projects and folders, keep several open at once, and know when and how they save.
- [Parts](https://docs.flozu.app/guides/parts.md): Add parts to a map, name them, say what they're built with, and move, select and delete them.
- [Lines](https://docs.flozu.app/guides/lines.md): Connect parts with requests, messages and uses lines, from any side, run them curved, square or straight, and pick what moves along them.
- [Make it look right](https://docs.flozu.app/guides/looks.md): Start from a preset, size the big pieces of your system big, pick each card's layout and drawing, and use colour to mark out regions, teams or the path that matters.
- [Zones and notes](https://docs.flozu.app/guides/zones-and-notes.md): Draw frames around parts that belong together, such as a cloud region or a team, and leave notes for whoever reads the map.
- [Maps inside parts](https://docs.flozu.app/guides/maps-inside-parts.md): Give a part a map of its own, such as a payment service's modules and what they call, and go in and out of it like zooming into the card.
- [Templates](https://docs.flozu.app/guides/templates.md): Start from an example system, from a static site to a whole delivery platform, and try a scenario on it.
- [Map your code with Claude](https://docs.flozu.app/guides/map-your-code.md): Have Claude read a codebase on your computer and write an outline of it, then import the outline and Flozu draws the map.
- [Connect an assistant](https://docs.flozu.app/guides/connect-an-assistant.md): Add Flozu to Claude Code, Claude, Cursor, VS Code, Codex, Windsurf, Gemini CLI, ChatGPT or another AI assistant, so it can map your code into your account and work with your maps.

## Test it

- [Traffic and limits](https://docs.flozu.app/guides/traffic-and-limits.md): Give lines their rates and parts their capacity, limit and buffer, let parts auto-scale, and see how each part copes.
- [Scenarios](https://docs.flozu.app/guides/scenarios.md): Ask "what if?" of a map, such as Black Friday or a product launch, play it over time, see which part runs short first, and apply the fix.
- [Failure drills](https://docs.flozu.app/guides/failure-drills.md): Pull the plug on a part, a line or a whole zone in a scenario, see what fails and what takes over, find the parts your map can least afford to lose, and try the fixes in a proposal.
- [Response times and cost](https://docs.flozu.app/guides/response-times-and-cost.md): See roughly how long requests take where traffic starts, how much of it fails, and what the map costs to run, while a scenario plays, and what a fix does to each.

## Share it

- [Presenting and share links](https://docs.flozu.app/guides/presenting-and-sharing.md): Show a map read-only to clients and colleagues, and send a link that carries the whole map, which nobody needs an account to open.
- [Stories](https://docs.flozu.app/guides/stories.md): Walk people through a map one step at a time, like slides, with each step framing the parts it's about and the load at that moment.
- [Versions and proposals](https://docs.flozu.app/guides/versions-and-proposals.md): Save versions of a map to look back on, propose changes in a copy, compare any two side by side with a scenario playing on both, and adopt a proposal.
- [Import and export](https://docs.flozu.app/guides/import-export.md): Save a map as a picture, a PDF or a file, move whole projects between computers as one bundle, and bring anything Flozu made back in.

## Accounts and teams

- [Your account](https://docs.flozu.app/guides/accounts.md): Sign in to keep your maps online and open them anywhere, continue as a guest to keep them in this browser, and download or delete everything Flozu keeps about you.
- [Teams](https://docs.flozu.app/guides/teams.md): Make a team, invite people by email with a role each, share maps with them, and archive the team when you're done.
- [Usage](https://docs.flozu.app/guides/usage.md): See how much of the beta's fair-use limits your account or team uses.

## The Mac app

- [The Mac app](https://docs.flozu.app/mac/overview.md): Flozu in its own window, with a native menu bar and every map saved as a file you can see in Finder.
- [Files and folders on a Mac](https://docs.flozu.app/mac/files-and-folders.md): Where the Mac app keeps your maps, projects and versions, and how Finder and Flozu stay in step.

## Concepts

- [The map](https://docs.flozu.app/concepts/the-map.md): What a Flozu map holds, from parts and lines to zones, notes, views, stories and scenarios, and the rules that keep it consistent.
- [How traffic is worked out](https://docs.flozu.app/concepts/how-traffic-is-worked-out.md): How Flozu turns a map's rates and limits into load, backed-up work, copies and suggestions, at one moment and over time, and how it estimates response times and cost.
- [Commands and undo](https://docs.flozu.app/concepts/commands-and-undo.md): Every change to a map is a small command, which is why undo always works and why an assistant can build maps safely.
- [Where maps live](https://docs.flozu.app/concepts/where-maps-live.md): Where your maps, folders and versions are kept, in your browser, on your Mac or in your account, and what that means for privacy.
- [Views](https://docs.flozu.app/concepts/views.md): One map, shown to different audiences, with things hidden and plain-language wording, without ever drifting apart.

## Reference

- [Keyboard shortcuts](https://docs.flozu.app/reference/keyboard-shortcuts.md): Every key in Flozu, for building maps, moving around, scenarios, stories and the Mac app.
- [Part kinds](https://docs.flozu.app/reference/part-kinds.md): Every kind of part, the key that adds it, what it's for and what usually comes after it.
- [Presets](https://docs.flozu.app/reference/presets.md): Every ready-made part on the library's Presets shelf, with its kind and what it is.
- [Drawings](https://docs.flozu.app/reference/drawings.md): Every drawing in the library, by category, with what it shows and the kinds it suits.
- [Ready-made scenarios](https://docs.flozu.app/reference/scenario-presets.md): The scenarios the scenario panel offers out of the box, and what each one tests.
- [File format](https://docs.flozu.app/reference/file-format.md): What's inside a .flozu.json map file and a .flozu-bundle.json bundle, how Flozu checks them, and how older files keep opening.
- [Glossary](https://docs.flozu.app/reference/glossary.md): The words Flozu uses, in one place.

## Help

- [Getting help and sending feedback](https://docs.flozu.app/help/getting-help.md): The Help menu, the question mark at the top right, leads to these docs, a short feedback form, the support address and the legal pages.
- [Questions and answers](https://docs.flozu.app/help/faq.md): Answers to common questions about Flozu, from where maps are kept to how accurate scenarios are.
- [Troubleshooting](https://docs.flozu.app/help/troubleshooting.md): What to do when you can't sign in, a map won't import, a link won't open, traffic doesn't move or a key does nothing.
- [Writing the docs](https://docs.flozu.app/help/writing-the-docs.md): How these docs are built, where each page lives, and how to keep them in step with the app.

## For assistants

- [Map a codebase into Flozu](https://docs.flozu.app/map-your-code.md): The steps an assistant follows to read a codebase and write a map Flozu can import.
- [All of the docs](https://docs.flozu.app/llms-full.txt): Every page above in one file.