About Engineering Utility Platform

Engineering Utility Platform is a collection of small, precise tools for the work engineers actually do between the interesting parts of their day: reading a payload, checking a token, planning an address range, working out what a cron line means. There are 32 of them today, and the platform is built to hold several hundred without becoming a directory of near-identical pages.

How it is built

The site is a Django application rendering server-side HTML, with each tool's logic as a small, tested JavaScript module that runs in your browser. There is no single-page app, no client-side router and no framework runtime to download before the page becomes useful — which is why tool pages are interactive as soon as they arrive.

Tools are declared in one registry. A tool definition carries its slug, category, description, metadata and behaviour flags, and routing, navigation, search, the sitemap and the JSON API are all derived from it. Adding a tool means adding a definition, a workspace fragment, a controller and its content — never touching layout or routing.

What happens to your data

For every tool marked Runs in your browser, nothing you type is transmitted. Not to us, not to anyone. The transformation happens in JavaScript on your machine, and you can confirm it in your browser's network tab — there is no request to inspect. That is also why there is no "save" feature and no history of your inputs: keeping them would mean having them.

Favourites, recently-used tools and display preferences are stored in your browser's local storage, which we cannot read. The privacy page has the details, including the one thing that is counted.

How it is funded

Eventually through unobtrusive advertising alongside the content, and through optional paid API access for teams who want to call these transforms programmatically. Advertising will never appear inside a tool's workspace, and there will not be a version of this site where formatting JSON requires an account. The tools stay free.

Requests and corrections

If a tool is wrong, missing an option, or simply missing, that is worth an email: contact@vertexonesolutions.com. Precise bug reports about edge cases are especially welcome — most of them turn into tests.