A ArchDevTools
// why this exists

About ArchDevTools

ArchDevTools started from a familiar frustration: evaluating a new tool for a team meant opening fifteen tabs, digging through pricing pages that obscure the real cost, and discovering what self‑hosting truly involves only weeks after the decision was made.

This is an attempt at the reference that should already exist — a directory of self‑hosted alternatives and open‑source tools, written for architects and tech leads who have to live with the decision, not for a general audience skimming a listicle.

Alongside the directory, we also provide a growing set of common developer utilities available freely — like encoder/decoder tools, a JWT token reader, and more everyday helpers that make technical work smoother.

Values

Transparency

Affiliate links are marked, sponsorships are disclosed, and reviews say where a tool falls short, not just where it wins.

Community

The tools directory grows from submissions, not just one person's stack. Credit goes to whoever found the tool first.

Quality

Every listing gets an honest look before it's published — no auto-generated filler entries padding out a category count.

Openness

Self-hosted and open-source options are surfaced right alongside SaaS, with the actual trade-offs, not just the SaaS pitch.

Who's behind this

ArchDevTools is run by Tech Leads/Architects — built and maintained as a working reference, not a full‑time media operation. Reviews reflect actual hands‑on use, not a vendor briefing.

How to contribute

Found a tool that belongs in the directory? Think an existing entry is wrong or out of date? The Community page covers how submissions work — short version: open a GitHub issue, it gets reviewed, and you get credit if it's added.