My startup · Hyndr
Hyndr: an internet health check, built and launched in 10 days
My early-stage startup. hyndr.in measures speed, ping, jitter and delay under load, then explains the result in plain words. Designed, built and launched in 10 days.
- Role
- Founder · design, backend, frontend and infrastructure
- Company
- Hyndr (founder)
- When
- Oct 2026 – present
- Status
- Live · early-stage, pre-incorporation
Visit hyndr.in (opens in a new tab)
- from first build day to public launch
- 10 days
- automated backend tests
- 300+
- fixes in the recommendation engine
- 22
Hyndr Box and the Hyndr Desktop App are in development and not yet released.
The problem
A speed test gives you one number. People whose video calls stutter or whose games lag often have a fast connection on paper, and the test does not tell them why things still feel slow.
Hyndr is a free internet health check. It measures download and upload speed, ping, jitter and delay under load, explains the result in plain words, and suggests safe next steps. No account is needed.
My contribution
I founded Hyndr and built it myself. I started the documentation on 29 September 2026, started building on 1 October, and launched hyndr.in on 11 October.
- Backend: an ASP.NET Core API on .NET 10, with 27 REST endpoints across 17 controllers, EF Core and PostgreSQL on Neon.
- Testing: more than 300 automated backend tests (unit and integration), plus contract tests that keep the API and the frontend in agreement.
- Frontend: Angular 22 with standalone components and signals, prerendered and hosted on Cloudflare Pages.
- Edge: a Cloudflare Worker that acts as a light test server close to each visitor.
- Infrastructure: Docker behind Caddy on a GCP VM, GitHub Actions deploying to separate Acceptance and Production environments, and monitoring with Grafana, Prometheus and Loki.
Technical decisions
Each of these is written down as an architecture decision record in the repository.
- A modular monolith. One API process, split into Domain, Application, Infrastructure and Persistence projects with dependencies pointing inwards. It is simple and inexpensive to run now, with boundaries that keep options open later.
- Stateless, signed test sessions. The chosen server and the byte and time budget for a test are signed into a short-lived token, so the API can validate requests without storing a session record.
- Never store test payloads. Download data is generated while streaming, and uploaded data is counted and thrown away. Hyndr needs the timing, not the bytes.
- The backend owns the score. The browser measures; the backend validates the facts and calculates the result, so the same connection gets the same verdict on every browser.
- Privacy by default. The full test works without saving anything. A limited summary is stored only if the person opts in, and usage insights are anonymous daily counts with no IP address or identity.
- Advice that learns. The recommendation engine ranks 22 real fixes by how much of the problem each removes against the effort it takes, and when someone says they tried a fix, the next check measures whether it actually helped.
Outcome
- hyndr.in went from first build day to public launch in 10 days.
- 300+ automated backend tests, a full deployment pipeline across Acceptance and Production, and production monitoring from day one.
- Next: the Hyndr Desktop App for background monitoring and history, and Hyndr Box, a small inline network device. Both are in development.