The KhaBot mission, in five notes, part 2 of 5

Paying for what you didn't use

Step one: one key, paid per use.

Khalil Ben Zineb4 min read

Last month you paid for things you did not use. I did too.

It happens in two ways. Some services charge you before you start. Others keep charging after you stop. Step one of the KhaBot mission exists to end both, so I want to show you each of them.

Before you start

Take a small job.

You need thirty minutes of generated voice. A hundred requests to a scraping service. A little work from a few AI models. A thousand image searches.

Add up what you really use, and the job costs about $7.

Now try to buy it. The four services will not sell you $7. The first one asks for at least $5. The second, $25. The third, $3. The fourth, $5.

You pay $38 for a $7 job.

The other $31 stays behind, in four accounts you may never open again. And you now have four passwords, four dashboards, four keys and four billing pages, for one afternoon of work.

A minimum payment is a tax on trying.

Look at who pays that tax. The student. The freelancer with a one-time job. The small business testing an idea. The person who is only curious. The people with the least money are asked to pay the most for nothing.

After you stop

The second way is quieter.

Imagine you take three months off. A real break.

Every subscription you have keeps charging you. To stop them you would have to cancel each one, and each has its own billing date. You would have to download your data from each one, and some do not let you. Then, when you come back, most of them will not let you put your data back where it was.

So nobody does it. We pay for three months of nothing.

Now imagine that in the middle of that break you must work for three urgent days. You pay for a whole month. The other twenty-seven days are a gift to the company.

It gets worse. A feature that costs ten cents to run is sold as a fifty-dollar monthly upgrade. A whole storage plan is sold to someone who went over the limit by two gigabytes.

I have more examples than I can count. Every one of them makes me angry in the same way. The cloud has been billed by the second for years. Somewhere between the machine and me, the seconds turn into months.

The rule I wanted

I wanted one rule. I pay when I use something. I pay nothing when I don't.

That is how KhaBot works. There is one balance. Each request costs what the provider charges, and KhaBot's fee is taken once, when you add credit.

Yes, KhaBot charges for everything. Even reading one small document from storage has a price. It is a tiny price, and it is published. That is the deal. Every small thing has a price, and nothing has a price when you do not use it.

So the small job from before takes $7 from your balance. The rest stays yours, for whatever you do next.

What it makes possible

Once you pay only for use, things that sounded silly become normal.

A server that exists for the length of one meeting. You start it, you hold a private call for three hours, you download the recording, and you delete it.

A machine with 24 CPUs for a job that happens once a month. It starts on a schedule, does the work, and stops.

A company server that is small on Sunday and large on Monday morning.

And the three months off. You back up everything to your own disk. You come back, and you upload it again. The bill for those three months is zero. If three urgent days come in the middle, you pay for three days.

When you stop a machine, it is saved. From then on you pay for its storage only.

One dollar

On KhaBot, a single dollar can start a strong server, run a model for a couple of minutes, and make a call or two to other services.

The machines are not cheaper. There is simply one balance, and every cent of it can go anywhere.

What I got back was more than money. It was quiet. One balance. One place to look. Nothing renewing while I sleep.

This is only step one. Everything else in the mission stands on it.

If you want to see it in numbers, the pricing page has an estimator. Move the amount and see what your money does.