Design preview · Try the local Tomato prototype. Hosted sync, payments and future apps are still planned.

AN INDEPENDENT SOFTWARE EXPERIMENT

Useful software.
Tiny bills.
No subscription
traps.

Fair Ninja is an experiment in building profitable software without designing against the people who use it.

Our apps work locally where possible. Hosted services like sync use tiny amounts from a shared prepaid wallet.

Our direction: no default auto-renew. Exportable data.
Core features that survive a server outage.

THE FAIR NINJA DEAL 01 / START SMALL
Your software.
Your time.
Your choice.

On your device

Your everyday work stays local.

YOURS

On our servers

Optional services. Prepaid usage.

PLANNED
No countdown. No catch.Just a different agreement ↗

Software got cheaper to build.
We think it should get cheaper to use too.

THAT’S THE EXPERIMENT. ↓

SMALL TOOLS. ONE SHARED FOUNDATION.

We’re starting with Tomato.

More Fair Ninja apps are coming.
One useful product at a time.

Planned

Habit

Routines that fit your life. Progress without pressure.

On the roadmap · no launch date
Planned

Todo

A small, useful home for the things you want to do.

On the roadmap · no launch date
Planned

Board

Simple boards to give your work a little more shape.

On the roadmap · no launch date
Now: refine Tomato. Next: explore Habit, Todo and Board. Readiness decides what ships.

THE ECONOMICS / INTENDED MODEL

Pay for the service, not for the
privilege of opening the app.

Local is yours. Sync is our service.

01

Use locally

Core functionality should work on your device.

02

Add chips

Prepay when you want. One wallet works across Fair Ninja apps.

03

Use sync and hosted features

Cloud functionality consumes tiny amounts based on usage.

04

See the bill

Understand where your chips went.

IN DEVELOPMENT

Hosted sync and the shared wallet are planned. Final rates are not published. No default auto-top-up. No payment is taken here.

WHY THIS EXISTS

We think software
incentives are
backwards.

A company should make more money because people choose to use a good product.

Not because they forgot to cancel it.
Not because the cancel button was hidden.
Not because an email scared them into returning.
Not because their data became difficult to move.

“We want to make money because you choose to use our software — not because you forgot to cancel it.”
Brave Beaver, the Fair Ninja mascot

Developers deserve to get paid.
Users deserve not to be trapped.BRAVE BEAVER / SMALL MASCOT, STRONG CONVICTIONS

01

Fair to users

Understandable pricing. Respect for your attention. Data you can take with you. No fake urgency or hidden exits.

02

Fair to developers

Infrastructure, maintenance, security and support are real work. The people doing it deserve to be paid.

03

Fair to reality

Show what works, what broke and what is still a plan. No invented traction, prices or promises.

A FAIR DEAL GOES BOTH WAYS

Fair does
not mean free.

Servers cost money. Security costs money. Maintenance costs money. Developers cost money.

AI helps us build faster. It does not make responsibility disappear. We want Fair Ninja to be profitable enough to maintain excellent software for a long time.

Fair means sustainable for us and obviously worth it for you.

BUILT AROUND YOUR DEVICE

Our server going down should be an inconvenience, not a disaster.

A timer should still time. Your local data should still exist. Sync can wait until the server comes back.

See what works locally
Your deviceTimer · tasks · local historyKeep working.
Sync can wait
Our serversHosted sync · plannedConnection unavailable

THE EXIT PROMISE / IN DEVELOPMENT

What if Fair Ninja
disappears?

Companies do not live forever. We can design for failure.

We are building toward an Exit Promise designed to give users and the community a path forward if Fair Ninja permanently shuts down its hosted services.

Read the intended Exit Promise

Our target is continued local functionality where technically possible, exportable data, documented formats and migration guidance. We intend to release the essential server code or tooling under an appropriate open-source license if hosted services permanently shut down.

This is a direction, not a completed guarantee. Source escrow, release triggers, licensing and self-hosting documentation still need technical and legal work.

OPEN REPORT / NOT PUBLISHED YET

Trust is easier
when there are numbers.

We intend to publish monthly operating reports covering real usage, chips, refunds, infrastructure, incidents and development.

Not every internal company metric. Enough to let you judge whether we are keeping our side of the bargain.

FAIR NINJA / OPEN REPORT PLANNED
Usage & chips consumedPending
Wallet deposits & refundsPending
Infrastructure & payment costsPending
Incidents, fixes & apps shippedPending

No measured report yet.
Missing numbers stay missing.

OPEN CONNECTIONS / PLANNED

Your tools should
work together.

API access, MCP and webhooks are part of the direction. The current connection screens are designs, not live services.

Explore connection designs

Shared identity, wallet and sync are intended foundations for future apps.

A FEW STRAIGHT ANSWERS

The details matter.

Why pay for sync?

Reliable sync needs servers, storage, monitoring, security, maintenance and support. Our intended model charges for that hosted service through a prepaid wallet. Local work should not depend on a recurring payment.

Are all subscriptions unfair?

No. Continuously operated services have real recurring costs. We object to profit from inattention, misleading prices and making it harder to leave than to join.

What is a chip worth?

Chips are the planned unit of a shared prepaid balance, not a cryptocurrency or investment. Final conversion rates and service prices are not published yet. No payment is taken in this preview.

What happens when my balance runs out?

The intended model pauses paid hosted services, not core local functionality. Auto-top-up will be off by default. Wallet and sync behavior are still planned in this prototype.

Can I export my data or leave?

In the Tomato prototype, open the data panel to export your workspace as JSON or sessions as CSV. Account deletion and refunds will need clear, discoverable paths when accounts and payments are available. This preview does not create an account or take payments.

Will you email me if I stop using an app?

Inactivity is not an emergency. We do not plan guilt-based reactivation emails. Account, security and important service messages serve a different purpose. Optional editorial email must be separate and explicitly requested.

USEFUL SOFTWARE. FAIR INCENTIVES.

Can fair software
become a great business?

We do not know yet. That is the experiment.
We think radically lower prices, honest incentives, useful software and massive scale can work together. And we would like to prove it.