Tomato
Focus, recurring tasks, useful time reports and open connections.
01 / EXPLORE THE MOCKFind your focus ↗AN INDEPENDENT SOFTWARE EXPERIMENT
Software got
cheaper to build.
Let’s make it
cheaper to use.
Good software. Normal features. Radically different economics. A growing family of apps, one prepaid wallet, and no monthly subscription.
Works offlineYou own your dataNo subscriptions
FAIR.NINJA / BEAVER MATHSAMPLE
$0.471 / month
Five apps. One illustrative bill.
47.1000 chips · demo rate: 1 chip = $0.01
Tomato · find your focus$0.020
Habit · build a rhythm$0.041
Todo · make a plan$0.110
Board · see the work$0.270
Notes · keep an idea$0.030
Automatic renewalOFF
A model to test, not measured usage or final prices. Upcoming apps are concepts.
Small bill. Nothing swept under the rug.Brave Beaver wants you to see the maths.
YOUR FIRST APP IS JUST THE BEGINNING
Build your own toolkit.
Use one app or a few. Keep your work locally. When you use hosted services, spend from the same wallet.
Habit
Routines that fit your life. Your progress, without the pressure.
02 / NEXTSee what’s planned →Todo
A home for your tasks, projects and everything coming up.
03 / PLANNEDSee what’s planned →Board
Give your project shape. Move the work forward together.
04 / PLANNEDSee what’s planned →One family, with shared building blocks. Notes and other tools are future ideas, chosen with community feedback.
MEET BRAVE BEAVER
“Developers deserve to get paid.
Users deserve not to be trapped.”
Small mascot. Fairly strong convictions.
THE FAIR PART IS FOR BOTH SIDES
Good tools.
A fair agreement.
We think AI and reusable foundations can lower the cost of building useful software. We’re testing that idea in public — including what it costs to keep it working.
01
Works offline.
Your everyday work stays available on your device. Online connections need a connection. Your timer doesn’t.
02
You own your data.
Keep a local copy, export your work, move on when you want. Leaving should be straightforward.
03
Pay for use. Skip the subscription.
Choose a top-up. See published rates. No default auto-renewal, and a clear margin to fund the people building your tools.
OPEN BY DEFAULT · THE BUSINESS TOO
Show the numbers.
Even the awkward ones.
Usage, costs, mistakes and what we learned. This is where the first measured report will live.
Active people · last 30 days—Awaiting measured data
Apps per active person—Meaningful use, not installs
Median monthly usage—Chips + money, side by side
After-infrastructure margin—Other costs reported separately
Top-ups ≠ usage. Unspent credit ≠ profit.Explore an illustrative bill →
What will a monthly Open Report include?
Active users and the measurement method; apps per person; top-ups, consumed services and remaining purchased/promotional balances; average and median bills; infrastructure, payment fees, AI, support and development costs; refunds, incidents and fixes. Missing data stays marked as missing. Negative results belong in the report too.
BUILDING IN PUBLIC
The work is the story.
One honest article, then useful excerpts where people discuss the problem. These are editorial drafts, not published results.
DRAFT IDEA / BEAVER MATH
“I made 1.8 cents
from myself.”
A two-cent bill can leave 90% after infrastructure. Here is what that percentage doesn’t pay for yet.
Read the draft outline
Start with an explicitly illustrative $0.020 charge and $0.002 infrastructure cost. Explain the remaining $0.018, payment fees, support and development. Replace the example with evidence before presenting it as an actual result.
DRAFT IDEA / THE FACTORY
What our second app
actually reused.
Fair Core, AI spend, human time and the parts that still had to be rewritten.
Read the draft outline
Compare Tomato and Habit development with the same cost categories. Separate new app work from improvements to Core. Report maintenance and regressions as well as initial build time. No savings percentage is claimed yet.
DRAFT IDEA / CHAOS BEAVER
Good thing we broke
our own billing first.
Duplicates, interrupted sync and a bill that must explain itself. Quality is part of the experiment.
Read the draft outline
Document a real failure once found: version, expected debit, observed ledger, reproduction, fix and regression evidence. A funny headline never substitutes for a real incident and an honest explanation.
FAIR CORE / THE FACTORY FLOOR
Build the foundation.
Keep getting better at it.
A proposed shared core for data, billing, sync, integrations and quality. The goal: a new app or meaningful release every 1–2 weeks once that foundation is ready.
TomatoHabitTodoBoard
Fair Core
Identity · wallet · metering · ledger · offline & sync · import / export
Permissions · UI · notifications · API / MCP / webhooks · releases & QA
Planned quality team · agent reports plus real people. These roles are a design for the factory, not a claim of running infrastructure.
Functional QADoes the promised workflow work?
Chaos BeaverWhat breaks when things go wrong?
Fresh UserCan someone find the first step?
UX ComparisonHow does the same job feel elsewhere?
CompetitorWhat changed, with a dated source?
Billing AuditorAction → usage → rate → ledger → bill.
SecurityWho can access or change what?
AccessibilityCan more people use every flow?
Feedback AnalystWhat do real reports tell us?
Evidence before badges: each report needs a version, expected result, reproduction and a traceable finding. Humans make release decisions.
OPEN TO YOUR TOOLS AND YOUR AGENT
Connect the useful parts.
Direct adapters, automation recipes and open interfaces. Your tasks and time can become a plan, a calendar block or a report.
MCP serverREST APIWebhooksIFTTTZapierMaken8n
Connections are mock flows. Your conversation and analysis stay in your external client. fair.ninja runs no AI model. Third-party services have their own terms; local work stays available offline.
BEAVER TEST COLONY
Break our apps.
Tell us what sucks.
Help turn a good idea into tools worth keeping. Try a real task. Point out what confused you. See what your feedback changes.
20→50→100→500
Recruitment targets, not current members. The program is a concept; this page does not collect sign-ups.
01 / Try something you actually do.
A recurring task, a client timesheet, a day planned with your agent. Useful work makes useful feedback.
02 / Tell us where it fell apart.
What you expected, what happened and enough detail to try it ourselves.
03 / Help check the fix.
A clear response, a visible change and a chance to say whether we got it right.
Useful feedback deserves thanks.
Proposed chip rewards for helpful reports and reproducible bugs. Never for positive reviews, stars or votes.
WHAT WE BUILD NEXT
A direction. In the open.
Tomato → Habit → Todo → Board. Readiness decides whether a release is an alpha, beta or finished app. No invented votes or promised launch dates.
NOW / TOMATO
Focus & time.
Review the mock, refine the daily flows and make the first bill understandable.
NEXT / HABIT
Find a rhythm.
Put recurring work and shared foundations to use for a new audience.
THEN / TODO
Make a plan.
Bring existing tasks in and keep the same data useful across apps.
THEN / BOARD
See the work.
Build on the core for cards, projects and more ways to organise work.
How will feedback shape later apps?
Look at recurring jobs, migration needs, demand and what Core can support well. Notes, calendars and other utilities are ideas, not a predetermined catalogue. Show the reasoning and actual feedback before claiming community support.
TOGETHER, BEAVERS BUILD.
Start with one useful thing.
Try Tomato. Explore the maths. Help shape what comes next.