Talos Editorial Team

Editorial Team, Talos.tools

Working developers and designers who maintain the curation, comparisons, and CSS generators on Talos.tools.

About Talos Editorial Team

The Talos editorial team is a small group of working developers and designers led by Mian Shahzad Raza (founder) who curate and maintain the directory. The team's job is to keep the catalogue accurate and the comparisons honest. Practically, that means three things. First, every self-hosted app entry is checked against the upstream project at least once a year — projects that have gone unmaintained or changed licensing get flagged or removed, and any new features get folded into the entry's description and feature list. Second, every comparison is written by an editor who has actually deployed both apps in production; we do not aggregate comparisons from elsewhere or rely on documentation alone. Third, the CSS generators are checked against current browser behaviour — when a CSS property's browser support shifts (for example, when subgrid hit broad support or when backdrop-filter behaviour changed in Safari), the affected generator and its description are updated. We do not accept paid placement, sponsored entries, or affiliate-driven ranking. Where affiliate links appear, they are disclosed inline. Editorial decisions about what to include and how to rank it are made on technical merit only.

Years of experience: 10

Areas of expertise

Self-hosted application curation

We maintain entries for 200+ self-hostable applications across categories: file sync, photo libraries, password managers, media servers, productivity tools, monitoring, automation, and more. Each entry is deployed-and-tested before publication.

Comparison writing (technical, decision-support)

Side-by-side comparisons of the most common 'A vs B' decisions in the self-hosted world. We avoid feature-list-only comparisons in favour of concrete scenarios, gotchas the docs don't mention, and clear 'when to choose' guidance.

CSS and design-tooling QA

We re-test the CSS generators against the latest stable Chrome, Safari, and Firefox each release cycle, and we flag any output that no longer reflects current best practice (e.g., outdated vendor prefixes, deprecated CSS).

Topics covered

Elsewhere