fewbase

The problem

Freelancers and solo founders juggle a handful of small chores — tracking time, remembering which subscriptions renew when, checking that their sites and certificates are alive, sending invoices, answering customers. The tools for these jobs are usually built for teams: seats, workspaces, dashboards to configure before anything is useful.

fewbase takes the opposite approach: one small tool per job, built for a single person, all behind one account.

What we built

• Time Recorder — tasks, a timer, projects and tags, period reports exported to PDF, and a Telegram remote.
• Subscriptions Tracker — recurring payments with currency conversion and reminders; an AI feature reads a receipt or screenshot and fills in the form.
• Infra Tracker — uptime checks every 5 minutes, SSL expiry and certificate-chain changes, domain expiry, alerts and a daily digest.
• Invoices — invoices, quotes and credit notes as PDF in English, Russian or Estonian, each with a public link.
• Support — a hosted support portal and a one-line widget; the contact form on this very site runs on it.

Engineering highlights

One account for every product

A central hub owns identity, billing, email and the Telegram bot. The products keep no identity of their own and talk to the hub over internal service bindings. Adding a new tool doesn’t mean building sign-in, billing and notifications again.

Passwordless sign-in done carefully

Sign-in uses a short-lived magic link with no user enumeration. The link is consumed by an explicit action on the page rather than by opening it, so corporate mail scanners that pre-open links can’t burn it.

Billing without card data

Subscriptions, yearly plans and one-off purchases go through Stripe; card data never touches our servers. Switching from sandbox to live is a configuration change, not a redeploy.

Serverless and cheap to run

Every product is a small TypeScript service on a serverless edge platform with a SQLite-compatible database and object storage for files. Scheduled jobs handle monitoring checks, reminders and digests. There are no servers to patch, and running costs stay small enough to keep niche tools alive for years.

Testing and operations

The platform has roughly 370 test files across its services: unit and integration tests running against the real runtime and database, plus Playwright end-to-end tests for the main user flows. Its own uptime, certificates and domains are watched by Infra Tracker — the same product customers use.