jido.run is built with Phoenix LiveView, hosted on Fly.io behind Cloudflare. It measures traffic with Cloudflare Web Analytics and Plausible Analytics. It sends email through Brevo (Sendinblue).
Built with Phoenix LiveView, hosted on Fly.io behind Cloudflare. Domain registered in 2026.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries1 | ||
| – | 7 Nov 2026 | |
| Frontend Build Tools & CSS2 | ||
| 4.2.1 | 7 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks2 | ||
| – | 7 Nov 2026 | |
| CDN & Hosting2 | ||
| – | 7 Nov 2026 | |
| Analytics & Tag Management2 | ||
| – | 7 Nov 2026 | |
| Email Marketing & Lead Capture1 | ||
| – | 7 Nov 2026 | |
| Transactional Email1 | ||
| – | 7 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 7 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
abby.ns.cloudflare.comjosh.ns.cloudflare.combrevo-code:3891f148b23015bc4f35d5e1ad8e7635v=spf1 include:spf.brevo.com ~allgoogle-site-verification=sD8i8XZ1QVv0kOCO-Fi1slMvbIThmwcv6I3l4dXJJBMv=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.comUser-agent: * Allow: / Sitemap: https://jido.run/sitemap.xml
# Agent Jido [Agent Jido](https://jido.run) is a site for building reliable multi-agent systems on Elixir/OTP. ## Preferred retrieval - Append `.md` to canonical public routes to request markdown directly. - Example: [Why not just a GenServer?](https://jido.run/docs/reference/why-not-just-a-genserver.md) - Public routes with markdown support: - `/` - `/docs*` - `/blog*` - `/ecosystem*` - `/skills` - `/features*` - `/build*` - `/community*` - `/getting-started` - `/examples*` - For clients that do content negotiation, the canonical route also supports: - `Accept: text/markdown` ## Primary content hubs - [Docs](https://jido.run/docs) - [Blog](https://jido.run/blog) - [Ecosystem](https://jido.run/ecosystem) - [Skills](https://jido.run/skills) - [Features](https://jido.run/features) - [Build](https://jido.run/build) - [Community](https://jido.run/community) - [Examples](https://jido.run/examples) ## Discovery - [Sitemap](https://jido.run/sitemap.xml) - [Feed](https://jido.run/feed) ## MCP docs server - [HTTP endpoint](https://jido.run/mcp/docs) - Tools: `search_docs`, `get_doc`, `list_sections` - Scope: published docs only ## Rendered fallback pattern - If source markdown is unavailable, request the canonical route with: - `Accept: text/markdown`
| – |
| 7 Nov 2026 |
| – |
| 7 Nov 2026 |
| – |
| 7 Nov 2026 |
| – |
| 7 Nov 2026 |