webitcache

Always-on cache for small apps & devices

Small state, reachable from anywhere.

webitcache is a hosted micro-cache for the data your software keeps bumping into: counters, last-known state, checkpoints and readings. A device or script pushes a value over HTTPS and always reads the newest one back — with a UTC timestamp and a short history, without running a database of its own.

Start with the API Free plan
10
entries kept per account
255
characters per entry
1
HTTPS request to read or write
0
servers to maintain

The idea

A cache, not a platform

Most small projects do not need a database cluster. They need one dependable place to store the last value — and to read it back later from a different process, network or continent.

Counters that survive reboots

A sensor, a cron job or an embedded board keeps its total in webitcache. Flash it, move it, reset the device — the number is still there when it comes back online.

State for devices behind NAT

No inbound ports, no VPN, no public IP. Devices talk outbound over HTTPS; you read the same state from a laptop, a dashboard or another service.

History without migrations

Every write is timestamped in UTC and the last ten are kept. You get a tiny audit trail of how a value changed — no schema, no migrations, no cleanup jobs.

How it works

Three steps, then it is just HTTPS

Registration is e-mail based, because the token is the whole account.

01

Register

Send your address to /webitcache/register. We reply with a token, a ban-unlock token and a confirmation link.

02

Confirm

Open the link. From that moment the token can write and read — until then it is inert.

03

Push and pull

/webitcache/save stores a value; /webitcache/read returns the newest one with its UTC timestamp.

write, then read — one token, two requests 
curl -X POST https://webitcache.analogbrain.com/webitcache/save \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":"counter=1842"}'

curl -X POST https://webitcache.analogbrain.com/webitcache/read \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" -d '{}'

{"data":"counter=1842","timestamp":"2026-01-01T12:00:00.000Z"}
  • Latest value is always one request away — no polling infrastructure to build.
  • Every response carries a UTC timestamp, so the reader knows how fresh the state is.
  • Ten most recent entries are kept; the eleventh write drops the oldest one.
  • Idle accounts (180 days without activity) are removed automatically — no forgotten data.
  • Account deletion wipes the entries and invalidates the token immediately.

API

Everything is one POST away

Send the token in the Authorization: Bearer header. No SDKs, no versioning rituals — JSON in, JSON out.

MethodPathAuthWhat it does
POST/webitcache/register—Start registration, tokens delivered by e-mail
GET/webitcache/confirmtoken in linkConfirm the e-mail address and activate the token
POST/webitcache/saveBearer tokenStore a value (≤ 255 chars), keep the newest 10
POST/webitcache/readBearer tokenNewest entry plus UTC timestamp
POST/webitcache/historyBearer tokenUp to 10 entries, newest first
POST/webitcache/unbanBearer + unban tokenLift an IP ban for the calling address (20 uses)
POST/webitcache/deleteBearer tokenDelete the account and every entry
GET/healthz—Service and database health

Machine-readable schema: /webitcache/openapi.json

Limits & fair use

Free tier with firm edges

Limits exist so one misbehaving client cannot degrade the service for everyone else.

Data

10 entries per account, 255 characters each — the oldest one is dropped on overflow.

Token abuse

10 requests with a bad token ban the IP for 15 minutes, then 24 hours, then 7 days.

Traffic

More than 5 registrations per second from one IP bans it for 15 minutes; 15 requests to unknown endpoints ban it for 24 hours.

Recovery

Each account carries a separate unban token (20 uses) that lifts the ban for its current IP — spent only when a ban is actually removed.

Pricing

Start free, scale when the data grows

Every plan keeps the newest entries and timestamps them in UTC. Switching plans changes the limits of an existing account — no migration, no new endpoint.

Free

$0/month

  • 10 entries kept per account
  • 255 characters per entry
  • UTC timestamp + newest-first history
  • Unban token with 20 uses

For side projects, sensors and scripts that keep a single value.

Start free

Pro

$5/month

  • 1,000 entries kept per account
  • 500 characters per entry
  • UTC timestamp + newest-first history
  • Unban token with 20 uses

Longer payloads and a thousand entries of history per account.

Request Pro

Business

$7/month

  • 5,000 entries kept per account
  • 500 characters per entry
  • UTC timestamp + newest-first history
  • Unban token with 20 uses

Five thousand entries for fleets of devices and busy pipelines.

Request Business

Paid plans are activated on your account after a short e-mail exchange — the API stays the same.

FAQ

Questions that come up before the first request

Short answers about the free tier, limits and how an account is created.

Do I need to run a database?

No. webitcache stores the entries for you: your app sends one HTTPS POST and reads the newest value back whenever it needs it. No schema, no migrations, no backup job.

How many entries can one account keep?

The free plan keeps the 10 newest entries of up to 255 characters each. Pro keeps 1,000 entries of 500 characters, Business 5,000 entries of 500 characters.

What happens to the oldest entry when the limit is reached?

It is dropped automatically, so an account always holds its newest entries and never grows without bound.

How is an account created?

Register an e-mail address, confirm it from the welcome message, and the API token plus a ban unlock token arrive in the same e-mail together with a markdown instruction file.

Which endpoints does the API expose?

/webitcache/register, /webitcache/save, /webitcache/read, /webitcache/history, /webitcache/delete and /webitcache/unban — every call is a single HTTPS POST authenticated with a bearer token.

Give your devices one dependable place for state

Register an address, confirm it from the welcome e-mail and your account is ready — tokens, limits and copy-ready commands arrive with the message.

Start with the API API schema