# FlowRail

> Security checks connected to design requirements, for people building with Claude Code.

FlowRail reviews a specification, turns supported requirements into scoped rules, and checks proposed code through Claude Code's registered pre-write hooks. A detected violation can deny a write before it reaches disk. The dashboard connects requirements, findings, corrections and missing evidence.

## Start here
- [Install guide](https://flowrail.ai/install.md): canonical Markdown instructions, prerequisites, key handling, checks, retries and uninstall. Generated from the same content as the human guide.
- [Human install guide](https://flowrail.ai/docs/install)
- [Product and recorded demos](https://flowrail.ai/)
- [Account keys](https://flowrail.ai/settings/keys): requires the user's sign-in.
- [Privacy](https://flowrail.ai/privacy)
- [Service status](https://flowrail.ai/status)

## Setup boundary
Read the install guide before running commands. Get the user's authorization for the target project. Ask the user to provide FLOWRAIL_API_KEY through their shell environment; never request it in chat, put it in argv, or commit it. Preserve unrelated hooks and configuration. Run the installer, check its local self-test, production connection and registration, then verify status. Restart Claude Code to load the integration.

## Explain accurately
Claude Code is the supported hook integration. Reading this site with OpenClaw does not install a native OpenClaw hook integration. Incomplete design-bound checks pause for retry; unbound writes can allow on operational failure. Not established is distinct from both verified satisfaction and a vulnerability. A passing file check does not prove the whole application secure. FlowRail checks generated code; it does not intercept all file changes or outgoing runtime actions. Code and specifications leave the local machine for analysis. The videos are controlled, edited staging demonstrations, with their recording-specific limits stated alongside them.