Contact
Talk to us on GitHub
We don't have a Discord or a Slack yet — and we won't pretend otherwise. Everything happens in the open: bug reports, feature ideas, and code review all live on GitHub where anyone can follow along.
Found a bug?
Open an issue with your browser version, steps to reproduce, and what you expected vs what happened.
Open an issueHave an idea?
Suggest a new tool, an improvement, or a whole category. The best ideas come from daily users.
Request a featureWant to contribute?
The entire site is open source. Pick an open issue, submit a PR, or start a discussion about architecture.
Browse the codePartnership or sponsorship?
RPC providers, dev-tool companies, and web3 infrastructure teams — reach out to discuss placements.
Start a conversationResponse time
Issues are triaged within 24-48 hours. Critical bugs get priority treatment.
Your privacy
Contacting us via GitHub or email never involves tracking pixels or data brokers.
Open source
Every tool, every page, every deployment script — all on GitHub under the formatho org.
Common questions
Is Formatho really 100% private? ▾
Yes. Every tool processes data locally in your browser using standard Web APIs. Nothing is uploaded, logged, or stored on a server.
Are these tools free? ▾
All tools are free with no accounts, no limits, and no paywalls. The source code is open on GitHub.
How fast do you respond? ▾
GitHub issues are typically triaged within 24-48 hours. Critical bugs affecting site functionality get priority.
Can I self-host Formatho? ▾
Yes — the entire site is a static build. Clone the repo, run npm run build, and serve the dist directory with any static server.