Get paid by the kilobyte.
Point a hostname at Cladior and your site has sign-in and billing. A visitor makes one Cladior account, carries it to every other site on Cladior, and pays for exactly what they load.
For the sites a subscription never fitted
- Resume builders
- Reading sites
- Calculators
One record instead of a login page.
- Sign-in Visitors arrive with an account they already carry.
- Billing Every kilobyte in and out, at the rate you set.
- Consent They see that rate and agree before anything is charged.
- Free paths Mark what stays open. Your front page can too.
- Receipts Every request itemised, down to the bytes.
- Certificates Issued and renewed for your hostname.
- Locked rate A reader keeps the rate they accepted. New readers get your new one.
-
Nothing to rip out
The integration is a DNS record. Point it back and we are gone, with no code of yours to undo.
-
You keep your whole rate
Our 20% is added on top of what you set, never taken out of it. Set $0.0001 and you are paid $0.0001, because the reader pays $0.00012.
-
Search still gets in
Verified crawlers read your paid pages, checked by IP rather than a name anyone can type.
-
No card ever reaches you
Readers hold one balance and spend it everywhere. Your origin never sees a payment detail.
Every site needs auth and billing before it can charge a cent.
You can write it yourself, or point a DNS record at us.
app.post('/webhooks/stripe', async (req, res) => { const sig = req.headers['stripe-signature'] const event = stripe.webhooks.constructEvent(raw, sig, SECRET) if (event.type === 'invoice.payment_failed') await suspend(sub) if (event.type === 'customer.subscription.deleted') await revoke(sub) return res.json({ received: true })}) app.use(session({ store: new RedisStore(redis), secret: SESSION_KEY }))passport.use(new LocalStrategy(async (email, password, done) => { const user = await db.users.findUnique({ where: { email } }) if (!user || !(await argon2.verify(user.hash, password))) return done(null, false)})) return renderChapter(book, chapterId) const sent = Number(res.getHeader('content-length') ?? 0)await db.usage.increment({ userId, bytes: sent, at: startOfHour() })const invoice = await stripe.invoices.create({ customer, auto_advance: true })if (invoice.status === 'uncollectible') await suspend(userId)Click in and change a line.
Written yourself, auth and billing is a file of payment webhooks, sessions, password hashing and usage metering, and it is yours to maintain. With Cladior your visitor sees one screen showing the exact rate per kilobyte, agrees to it before anything is charged, and there is no equivalent file to write.
Neither side has to trust the other.
A kilobyte is not a judgement about value or effort. It cannot be inflated by the site or argued down by the reader. You and your reader are looking at the same number on the same meter.
What you both have to trust is us, so every charge is itemised on both sides, down to the bytes that produced it.
What stops being your problem.
Not features. The things that quietly eat a week and never appear on a roadmap.
- A signup form
They already have an account
No password to store, no reset email to send, no session to keep alive, and nothing of yours to breach.
- A month for one thing
One thing costs one thing
The reader who wanted a single page stops bouncing off a subscription, which is the audience most sites of this size never convert at all.
- Ads, because there was nothing else
The page pays for itself
A calculator or a reading site earns from the reading rather than from selling the reader's attention to somebody else.
- Deciding it is not worth it
One DNS record
The reason most of this never got built is that billing costs more than it returns until a site is large. That is the part this removes.
Your origin does not move.
Cladior sits in front of whatever already serves the site. Nothing is redeployed and nothing is rewritten, so the stack you picked stays the stack you have.
- Vercel
- Cloudflare Pages
- Netlify
- Google Cloud
- nginx
- Caddy
- AWS
- Your own server
One price cannot fit both.
Four things a product might return. The largest is sixty thousand times the smallest, so they only sit in one picture if every step along the scale is ten times the step before it.
Priced by the kilobyte, the first costs almost nothing and the last earns what it cost to serve. You never decide who is a Starter and who is a Pro, because nobody has to be either.
See how it is countedWhat that is to a reader.
Set a rate of $0.0001 a kilobyte and your reader pays $0.00012, our twenty percent included. That buys rather more than it sounds like.
- 12 KB A short page
- 38 KB A long article
- 220 KB A document or image
Five dollars of credit is about a thousand articles. A reader tops up once and stops thinking about it, which is the part a subscription never manages.
Listed where people go looking.
Every listed app appears in Explore, ranked inside its category by net votes. Placement is not for sale and we do not curate it.
Browse Explore- 01 Top of its category
- 02 Climbing
- 03 Newly published
Start with one record.
No code to write and no card on your site. The rate you set is the number that reaches you.