IT Tools

One Docker command. Every developer utility you reach for daily — Base64, JWT decoder, hashes, UUID, JSON formatter — running on your own server, ad-free.

TL;DR

• What it is: Open-source (GPL-3.0) collection of 100+ web-based utility tools for developers — Base64 encoder, JWT decoder, hash generators, UUID, JSON formatter, subnet calculator, and more [GitHub][1].
• Who it’s for: Developers and technical operators who are tired of Googling “base64 encode online” and landing on ad-filled, tracker-heavy sites. Also useful for teams wanting a shared, self-hosted toolbox without sending internal data through random third-party websites.
• Cost savings: The live version at https://it-tools.tech is free. Self-hosting on a VPS costs $5–10/mo — but realistically, many people self-host this alongside other tools on an existing server, making the marginal cost zero.
• Key strength: 37,651 GitHub stars, clean Vue.js UI, one-command Docker deploy, broad tool coverage across crypto, encoding, networking, text, and data categories [GitHub][1].
• Key weakness: GPL-3.0 license limits embedding in proprietary products. No user accounts, no history, no collaboration — it’s a stateless toolbox, not a platform. Project appears to have slowed development activity.

---

What is IT Tools

IT Tools is a single-page web application that bundles roughly 100+ developer utilities into one clean UI. You open a browser, pick a category, and get the tool — no ads, no sign-up, no data leaving your server if you self-host.

The pitch is simpler than it sounds: every developer maintains a mental list of websites they reach for daily. base64encode.org for quick encoding. jwt.io for decoding tokens. Some random SHA256 site for checksums. A bookmark folder of forgettable domains, most of them covered in ads, some that log your input, none that you’d trust with a production secret.

IT Tools replaces all of them. The project was built by Corentin Thomasset and has attracted a long contributor list — the README credits the community for a significant share of the tools [GitHub]. It’s been featured on Product Hunt (top post of the day) and is continuously deployed at https://it-tools.tech if you want to test it before self-hosting [GitHub README].

As of this review it sits at 37,651 GitHub stars — which, for a utility tool with no viral “AI-powered” angle, is a meaningful signal that developers actually use it [GitHub].

---

Why Developers Choose It

The third-party coverage on IT Tools specifically is thin — most of what exists is deployment guides rather than reviews [1]. So this section draws from what’s visible in the GitHub star count, community mentions, and the tool’s design choices.

The core reason is trust and speed. When you’re debugging a JWT at 11pm and you paste it into jwt.io, you’re trusting a domain you didn’t audit. When you paste a production API key into a hash site to verify a signature, you’re hoping that site isn’t logging inputs. IT Tools self-hosted means your internal data hits your server, not someone else’s.

The secondary reason is UX consistency. Instead of 15 different websites with 15 different layouts and 15 different cookie banners, you get one interface with a search bar. Techdox describes the deployment as straightforward Docker Compose work with port 8080 exposed — the kind of setup that takes under 10 minutes if you have Docker already running [1].

The third reason is less discussed but matters for teams: no external requests. A development team with an internal tools server can give everyone access to IT Tools without any data touching the public internet. For teams under NDA or working with financial data, this isn’t paranoia — it’s policy.

---

Features

IT Tools organizes its utilities into roughly these categories (based on the live site and README):

Crypto and encoding:

• Token generator (random bytes, various formats)
• Hash generators: MD5, SHA1, SHA256, SHA512, and others
• Base64 encode/decode
• URL encode/decode
• HTML entity encode/decode
• JWT decoder (decode and inspect a JWT without verification)
• AES encryption/decryption

Data and formatting:

• JSON formatter and prettifier
• JSON to YAML converter and reverse
• SQL formatter
• XML formatter
• CSV to JSON converter

Web and network:

• URL parser
• HTTP status codes reference
• IPv4 subnet calculator
• IPv6 address converter
• MAC address generator
• User-agent parser
• MIME types reference

Text and generation:

• Lorem ipsum generator
• UUID v1/v4 generator
• Password generator
• Text case converter (camelCase, snake_case, PascalCase, etc.)
• Markdown preview
• Text diff checker
• Regex tester

Measurement and math:

• Temperature converter
• Date/time converter
• Cron expression parser
• Color format converter (HEX, RGB, HSL)

What it doesn’t do: No persistence. No user accounts. No history of what you encoded last Tuesday. No API. No collaboration features. Every tool runs in the browser — inputs are processed client-side or server-side depending on the tool, but nothing is saved between sessions. This is a stateless toolbox, not a data management application.

The tool list grows through community contributions. The repo accepts pull requests for new tools via a scaffolding script [GitHub README], which explains the breadth — no single developer could maintain 100+ tools.

---

Pricing: SaaS vs Self-Hosted Math

IT Tools doesn’t replace a specific paid SaaS subscription the way Activepieces replaces Zapier. The math is different.

The hosted version (https://it-tools.tech) is free. No account, no payment. If you’re comfortable using a public site for non-sensitive tasks, you can use it today at zero cost.

Self-hosted on your own infrastructure:

• Software: $0 (GPL-3.0)
• Docker command: docker run -d --name it-tools --restart unless-stopped -p 8080:80 corentinth/it-tools:latest [1][GitHub README]
• VPS if you’re running nothing else: $5–10/mo (Hetzner, Contabo)
• If you already have a home server or VPS with spare capacity: $0 marginal

What you’re actually saving: The value isn’t replacing a subscription — it’s replacing privacy exposure and UX friction. Services like CyberChef Online, smalldev.tools, and similar “developer toolbox” SaaS products either push paid tiers for API access, run ads, or handle your input through their servers. If your team processes sensitive tokens, internal API keys, or customer data through these tools, the risk isn’t financial — it’s operational.

For teams with a data residency requirement or a security-conscious policy, self-hosting IT Tools is the only acceptable option. The math is: one docker run command versus explaining to your security team why you pasted a production JWT into a public website.

---

Deployment Reality Check

This is where IT Tools genuinely earns its reputation. The deployment is as simple as self-hosted tools get [1][GitHub README].

Minimum viable setup:

docker run -d --name it-tools --restart unless-stopped -p 8080:80 corentinth/it-tools:latest

Navigate to http://<your-server-ip>:8080 and you’re done [1]. No database. No environment variables to configure. No Redis. No SMTP. The entire application is a static frontend — there’s nothing to persist.

Docker Compose (recommended): Techdox documents a simple docker-compose.yml approach: define the service with the corentinth/it-tools:latest image, map port 80 to 8080, set restart: unless-stopped, and run docker compose up -d [1]. Total setup time for someone with Docker already installed: under 5 minutes.

Alternative deployment options:

• Cloudron (one-click from their app store)
• Tipi (runtipi.io app list)
• Unraid (community apps) [GitHub README]

What can go sideways: Almost nothing, by design. The application has no backend state, so there’s nothing to corrupt. Upgrades are a docker pull and restart. Rollback is pointing at a previous image tag.

The main operational consideration is HTTPS. If you’re exposing this to your team over a network, you’ll want a reverse proxy (Caddy or nginx) with TLS in front of it. Caddy handles this in about 10 lines of config. If you’re running it locally or on a trusted LAN, HTTP on 8080 is fine.

Realistic time to a working instance: 5 minutes for a developer who has Docker running. 30–60 minutes for someone setting it up from scratch on a fresh VPS including Docker install, domain DNS, and Caddy config.

---

Pros and Cons

Pros

• Zero-dependency Docker deployment. No database, no Redis, no environment variables. One command, one container [1][GitHub README].
• 37,651 GitHub stars. Not viral hype — developers bookmarked and starred this because they actually use it [GitHub].
• Broad tool coverage. ~100+ tools across encoding, crypto, networking, text, data, and generation — covers the vast majority of daily developer utility needs [GitHub].
• Stateless and private. No data stored, no accounts, no analytics on your inputs when self-hosted.
• Clean UI. Built in Vue.js by someone who cared about the interface — categorized, searchable, consistent. Not a collection of mismatched iframes.
• Free hosted version. https://it-tools.tech works today with no account if you want to evaluate before self-hosting.
• Active contributor community. New tools added via community PRs, with scaffolding script to make contribution straightforward [GitHub README].
• Available on Cloudron, Tipi, Unraid for homelab users who prefer GUI-based deployment [GitHub README].

Cons

• GPL-3.0 license. If you want to embed these tools in a proprietary SaaS product, GPL-3.0 creates licensing complexity. The free version at https://it-tools.tech is available but you don’t control it.
• No persistence or history. Every session starts fresh. If you encoded something important yesterday, you re-encode it today. No way to save snippets, share tool outputs, or build a team knowledge base around it.
• No collaboration features. No user accounts, no sharing links with outputs, no team workspaces. It’s a solo toolbox by design.
• No API. You can’t automate IT Tools or call its transformations from a script. It’s a UI tool only.
• Development pace has slowed. The project appears to have reduced active development based on GitHub activity. Issues accumulate. New tool requests in the issue tracker have stalled. For a stateless utility this matters less than for a platform, but it’s worth noting.
• No mobile optimization. The UI is designed for desktop browser use. Functional on mobile but not optimized.

---

Who Should Use This / Who Shouldn’t

Use IT Tools if:

• You’re a developer or technical operator who reaches for Base64/JWT/hash/UUID tools daily and wants them all in one place.
• Your team has data residency requirements and can’t use public online tools for sensitive inputs.
• You run a homelab with a Docker host and want a genuinely useful addition that costs nothing extra.
• You’re setting up a shared tools server for a development team.

Skip it if:

• You need persistence, history, or the ability to save and share transformed data.
• You want to embed the tools in your own product — GPL-3.0 requires your product to be GPL-licensed too.
• Your team is non-technical and would be confused by a 100-tool interface with no onboarding.
• You’re looking for something that automates workflows rather than just providing manual utilities.

---

Alternatives Worth Considering

• CyberChef (GCHQ, Apache 2.0) — the power-user’s alternative. Hundreds of operations, chainable into pipelines, offline-capable. Steeper learning curve, UI isn’t as clean, but dramatically more powerful for complex transformations. Better choice if you need to chain multiple operations.
• DevUtils — a native macOS app in the same category. Not self-hostable, $19.99 one-time or subscription. Better offline performance, but you’re back to a paid tool and it doesn’t run on a shared server.
• Hoppscotch — overlaps on the HTTP/API testing side. Different category (API client vs. utility toolbox), but worth knowing.
• smalldev.tools — similar concept, hosted SaaS. No self-host option, ad-supported on free tier.
• omatsuri.app — smaller tool collection, open source. Less comprehensive than IT Tools.

The practical comparison is IT Tools vs. CyberChef. IT Tools wins on UX clarity and ease of deployment for teams who want a clean shared toolbox. CyberChef wins on raw transformation power for security researchers and people who chain operations. For a development team’s daily utilities, IT Tools is the better default. For a security team doing data analysis and encoding chains, CyberChef is the right tool.

---

Bottom Line

IT Tools is one of those rare open-source projects where the value proposition is immediate: one Docker command, five minutes, and you have a clean, ad-free, private replacement for the scatter of sketchy online utility sites every developer has bookmarked. The 37,651 GitHub stars aren’t from marketing — they’re from developers who tried it and shared it. The deployment is genuinely painless [1][GitHub README], the tool coverage is broad, and the stateless design means there’s nothing to maintain beyond occasional image updates.

The limitations are real: no persistence, no API, no collaboration, GPL-3.0 license, and development activity that appears to have slowed. But for what it is — a shared, private, self-hosted developer toolbox — it delivers exactly what it promises with almost no setup friction. If you’re running a home server or a team development environment and you’re still Googling “base64 decode online,” this is a 10-minute fix.

---

Sources

1. Setting Up IT Tools with Docker Compose — techdox.nz. https://docs.techdox.nz/ittools/

Primary sources:

• GitHub repository: https://github.com/corentinth/it-tools (37,651 stars, GPL-3.0, Corentin Thomasset)
• Official hosted version: https://it-tools.tech
• Product Hunt listing: https://www.producthunt.com/posts/it-tools