Daedalus
Internal Developer Platform with 6 views (Developer, PE, CTO, PM/PO, Scrum Master, C-Level). Aether Telemetry as the nervous layer underneath.
The problem
Generic Internal Developer Platforms (Backstage, Port) deliver a catalog. But no CTO makes decisions with a catalog. They make decisions with correlation between cost, quality and velocity of the engineering team.
What Daedalus does
Daedalus is IDP + Engineering Intelligence, with 6 distinct views for 6 team audiences:
| View | Audience | Answers |
|---|---|---|
| Developer | IC engineer | ”Where’s the runbook? How do I deploy?” |
| Platform Engineer | PE | ”What services are we maintaining? Which fails most?” |
| CTO | CTO | ”Cost per team? Drift trend?” |
| PM/PO | PM | ”Which feature cost $X? How long did delivery take?” |
| Scrum Master | SM | ”Which team is blocked on whom?” |
| C-Level / Board | Board | ”Executive summary, no details.” |
Each view is the same data, aggregated differently.
The moat
Aether Telemetry underneath. Daedalus is the only IDP that correlates infra cost ↔ semantic contract violation in the same query. That correlation is only possible if your observability system preserves it — Datadog/New Relic don’t.
Current state
In design. Complete architecture, 6 views with individual SPECs. No repo yet.
Planned stack
Elixir · Phoenix · LiveView · SvelteKit (complex visualizations) · Broadway.
Want to talk about this?
If Daedalus resonates with a problem you're facing, book a 30-minute call to get into the detail.