Contact
GAIA FLOW is made by a small team at BRAHMA TECH. There is no ticket queue and no outsourced desk — a message about a broken cockpit is read by someone who can open the file it came from.
Where to write
Everything arrives at the same place. Naming the route in your subject line is what moves it to the right pair of hands on the first read.
Install trouble, a cockpit that will not draw, a brain that drifted out of sync, a command that behaved differently to its documentation.
What to expect
A written diagnosis or a workaround you can apply the same day, and a straight answer on whether it becomes a fix in the next release.
Questions about the lifetime licence, moving a licence to a replacement machine, renaming a machine, or buying several at once for a team.
What to expect
Checkout is not open yet, so this is where a pre-purchase question gets answered by a person rather than a policy page.
A vulnerability in the plugin, the installer, the launcher or the hooks. Write privately first — subject line SECURITY — and give us a chance to ship a fix.
What to expect
Acknowledgement that a human has it, our read on severity, and credit in the changelog when the fix ships, if you want it.
Teams standardising on GAIA FLOW, tool builders who want the brain format to interoperate, and anyone reselling or bundling it.
What to expect
A frank reply about fit and timing. The roadmap is public in the changelog, so we can tell you what is real today and what is not.
Send a message
Specifics travel further than adjectives: the command you ran, what you expected, what you got.
Picking a route only decides who reads it first.
Never paste secrets, tokens or licence keys. We do not need them, and we would rather they stayed on your machine.
The fields above are the real design, not a mock-up — but there is no endpoint behind them yet, so the button does nothing on purpose. We would rather show you an honest dead button than quietly drop your message.
Until it is wired, support@brahmatechs.com is the whole system, and it is read every working day.
Run /gaia-doctor in the affected project and paste its verdict. It checks the brain files, leftover placeholders, drift between the snapshot and the changelog, and the launcher — which is most of the first reply we would otherwise have to write.
$ /gaia-doctor expected files ok Project_Brain/02_CURRENT_STATE.md ok Project_Brain/PROJECT_MEMORY.md -- missing 06_CONVENTIONS.md placeholders ok none left over launcher -- RESUME.command not executable drift ok snapshot matches newest entry verdict needs your input on 2 items
The company
GAIA FLOW CLI is built and published by BRAHMA TECH, the software practice of Crown Troca Private Limited. The same people write the engine, the docs and the replies.
The product is terminal-first by conviction: everything it produces is plain markdown that stays in your repository, so nothing you write with it depends on us continuing to exist.
Before you write
If your answer is here, you have it now rather than tomorrow.
A licence is bound to a single machine, and on that machine it covers unlimited projects — every repository you point GAIA FLOW at. You can name each licence so a list of machines is readable rather than a list of hashes, and rename it when you replace the hardware.
A laptop and a desktop are two machines, so they are two licences. There is no seat count, no metering and no renewal.
Nothing has been sold yet — checkout opens after the public release, so there is no payment to refund today. The refund terms will be published alongside checkout, before the first purchase is possible.
Until then, ask anything you would want settled before paying and you will get a direct answer at support@brahmatechs.com.
Claude Code, OpenAI Codex CLI and Google Gemini CLI, on macOS, Linux and Windows.
There are no hard dependencies beyond a shell: no Node, no daemon, nothing to keep running in the background. python3 is optional — it deepens the intelligence layer, and everything still works on pure bash without it.
No. The Project_Brain is plain markdown written into your own repository, and the scanners read your files locally to produce it. Your source code is never uploaded.
The learning layer, which studies engineering patterns rather than code, is opt-in and secret-scrubbed. If you never turn it on, nothing at all is sent.
Nothing expires. The licence is one-time and lifetime, so there is no subscription to lapse and no state that stops working because you walked away for six months.
If you remove the plugin entirely, every note stays: Project_Brain/ is markdown, versioned in git, readable by any agent or any human. The brain outlives the tool that wrote it — that is the point of keeping it in the repo.
Privately, to support@brahmatechs.com with SECURITY in the subject. Include the version, the platform, and the smallest reproduction you have.
Please hold off on public disclosure until a fix ships. We will tell you what we found, what we changed, and when it landed — and credit you in the changelog if you would like to be named.
Early access
Checkout opens after the public release. Join the early access list and you will be told the day it does — one message, no drip campaign.
