Tiny Little Office is a free, MIT-licensed office suite that runs in the browser and keeps each document inside its own link, built for people who need to write a letter, a spreadsheet, a presentation or a calendar and hand it to someone else without an account, a sign-up or a file upload.

What it is

Tiny Little Office is a TypeScript web application, assembled from Lit web components and delivered as a progressive web app, that offers a word processor, an outliner, a presentation builder, a spreadsheet, a calculator, a drawing tool, a diagram maker, an animator, a calendar and a trip planner. It sits in this registry under Productivity & Utilities / Office Suites, and its topics — local-first, no-backend, cloudflare-workers, pwa, web-components and privacy — describe its shape accurately: no application server holds the work and no database sits behind the pages.

The problem it solves is document sharing without an account. In a conventional office suite the document lives in someone's storage and the link is merely permission to look at it: an account is needed to create the file, often another to open it, and the content sits on a server in between. Tiny Little Office removes that layer. A letter, spreadsheet, presentation or calendar is held in the address of its page, so copying the link copies the document, and whoever has the link has the document. That replaces the account-backed document store — the shared drive, the workspace, the attachment in an email — with the URL itself.

Key capabilities

• Ten document types, one per route: write for the word processor, outline for the outliner, deck for the presentation builder, sheet for the spreadsheet, calc for the calculator, draw for the drawing tool, diagram for the diagram maker, anim for the animator, cal for the calendar and trip for trip planning.
• Whole documents encoded into versioned link paths such as /write/#/v1/write/... and /sheet/#/v1/sheet/..., so the address itself carries the content.
• No account and no implicit save: nothing is stored unless the user chooses to keep it.
• Word processing with a title, task lists, tables that add up and footnotes.
• Presentations with a title slide, two-column layouts, charts and speaker notes.
• Spreadsheet bar charts, and a calculator covering tax, tip and a bill split six ways.
• Shipped as an installable PWA built from Lit web components, with no backend to run.

Who uses it and how

• Individuals sending a one-off document to someone who has no account anywhere, by pasting the link into a chat or an email.
• People who want to hand over the document rather than a permission, because the recipient needs only a browser.
• Teams that would rather not operate document storage, a database or a mail server to collaborate on a letter or a budget.
• Privacy-conscious users who prefer the document to live in the URL they hold rather than in a vendor's cloud.
• Self-hosters deploying the project to their own static or Cloudflare Workers hosting and pointing users at their own instance.

Getting started

The hosted instance at https://tinylittleoffice.com is the shortest route: open it, choose a document type and start writing. Self-hosting means deploying the TypeScript repository as the PWA it is, with Cloudflare Workers among the deployment targets its topics name.

How it compares

No comparable open-source projects appear in the facts for this entry, so Tiny Little Office stands alone in this registry as the only link-encoded office suite listed. It should be read on its own terms: MIT-licensed, self-hostable, and with no vendor account in the loop for either the author or the reader.

When to use it — and when not to

Choose it when the document is disposable, the audience is someone you can send a URL to, and you want no server, no account and no storage to maintain — the self-hoster operates static hosting only, with no database, object store or SMTP to keep alive. Do not choose it when you need access control, revocation or an audit trail: whoever has the link has the document, the link cannot be recalled, and the addresses grow long. There is no server-side history or backup either, and the repository carries around thirty open issues, so anyone needing long-lived, recoverable records should look elsewhere.

npm install
npm run dev      # the site at http://localhost:4178
npm test         # every test, under Node and in Chromium
npm run build    # the site as it ships