aitorevi Tools

The problem

Most online utilities make you upload your files to a server you do not control. For something as simple as splitting a PDF, converting an image or decoding a JWT, that means handing over private data in exchange for convenience. What if the tool needed no server at all?

The solution

• 100% in the browser

  Everything runs locally in JavaScript; files are never uploaded. There is no backend to maintain or that could leak anything.

• Vendored dependencies

  Ten libraries (pdf-lib, JSZip, sql-formatter, js-yaml, Prettier…) live in the repo pinned to an exact version, with no external CDN. The app depends on no third parties at runtime.

• aitorevi.dev identity

  Same tokens, fonts and navbar/footer as the main site, with class-based light/dark theme. It reads as part of the project.

• Actually tested

  Pure logic tested with Vitest and end-to-end flows with Playwright: 42 green tests.

Tech stack

Technical decisions

• Privacy by design

  With no server there is nothing to upload or store: files and text are processed in memory and downloaded straight from the browser. A strict CSP prevents the app from loading any third-party resources, and there is no analytics or cookies.

• No build, pure static

  HTML/CSS/JS served as-is, with vendored, version-pinned libraries. Deployed on Vercel with no build step: shipping is just uploading files.

• A scalable hub

  Each tool lives in its own folder and reuses shared styles, theme and fonts. Adding a new one is creating a folder and a card on the landing.

Screenshots

tools.aitorevi.dev landing with the grid of 21 tool cards organised in three sections: PDF, image and code

PDF splitter tool with a document loaded, showing the selectable pages and the buttons to download individually or as a ZIP

PDF merger tool with several documents queued, reorderable, ready to be combined into a single PDF