About

Every tool. One place.

OmniKitly is a universal utility workspace: documents, images, media, developer utilities and everyday digital tasks, built to grow to hundreds of tools without becoming a mess.

Why another utility site

Most online tool sites are either one good tool wrapped in ads, or a hundred mediocre ones behind a sign-up wall. We want the opposite: a toolbox that is fast to open, private by architecture, honest about what runs where, and organised so that the two-hundredth tool is as easy to find as the first.

Principles

  • Local first. If a task can run in your browser, it does.
  • Server when necessary. Some jobs need real hardware. The badge tells you before you start.
  • Account only when necessary. Bulk, workflows, history and API — not for merging two PDFs.
  • No fake claims. Not about privacy, not about compliance, and not about which features exist yet.

What is real and what is mocked in this build

This is a design and frontend-architecture prototype. Here is exactly where the line is.

Roadmap, in order

  1. Review and approve this prototype: navigation, search, tool workspace, result chaining, bulk, workflows, API and signing.
  2. Build the client processing engine for local tools (PDF.js, pdf-lib, Canvas, Web Workers, WebAssembly codecs).
  3. Stand up the jobs API, queue and isolated workers for server tools.
  4. Accounts, bulk dashboard and workflow execution on the shared engine.
  5. Signature requests, teams, integrations.

The full production architecture, including the security requirements every server tool must meet, is documented in README-ARCHITECTURE.md alongside this prototype.