SeeTheStackSeeTheStack| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries1 | ||
| – | 18 Oct 2026 | |
| CDN & Hosting1 | ||
| – | 18 Oct 2026 | |
| Analytics & Tag Management1 | ||
| – | 18 Oct 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 18 Oct 2026 | |
aspmx.l.google.comalt2.aspmx.l.google.comalt1.aspmx.l.google.comalt4.aspmx.l.google.comalt3.aspmx.l.google.comdenver.ns.cloudflare.comdaniella.ns.cloudflare.comgoogle-site-verification=lZ25eS-PASgpKIG6aDRHTPcO96c6GOwQvq67iMRRE5Uv=spf1 include:_spf.google.com ~allv=DMARC1; p=none; rua=mailto:34848266781149c09905971554f256a7@dmarc-reports.cloudflare.net# withadi.dev # # The line that matters is the last one: without a Sitemap directive there is # nothing on this domain telling a crawler what pages exist. dist/sitemap.xml is # generated from the pages that actually built (src/integrations/for-agents.ts), # and the build fails if this URL and astro.config.mjs's `site` ever disagree. # # The AI-crawler policy is NOT here on purpose. Cloudflare prepends its own # managed block — Content-Signal, and Disallow for GPTBot, ClaudeBot, CCBot, # Bytespider and the rest — to whatever this file says; verified live on # 2026-08-29, its "BEGIN Cloudflare Managed content" marker sitting above this # comment in the served file. A copy of that list lived here for one deploy, to # be safe about which file won, and came straight back out: Cloudflare keeps # theirs current and ours would have gone stale in place. User-agent: * Allow: / Sitemap: https://withadi.dev/sitemap.xml
# ADI > A month has 730 hours and yours are already spoken for. ADI runs agents on your own machine — you define each one, and it holds your tools, your data and the memory of the work. Every page here is also served as Markdown: fetch the .md below, or send `Accept: text/markdown` to the page URL itself and you get the same page. ## Pages - [ADI — agents on your own machine](https://withadi.dev/index.md): A month has 730 hours and yours are already spoken for. ADI runs agents on your own machine — you define each one, and it holds your tools, your data and the memory of the work. - [Privacy — what ADI knows about you](https://withadi.dev/privacy/index.md): ADI has no account system and no server holding your data. This page says what stays on your device, what our relays can and cannot see, what the software sends on its own — an update check and a listed set of usage events you can switch off — and what this website records. - [Security — reporting a vulnerability in ADI](https://withadi.dev/security/index.md): How to report a security problem in ADI or on withadi.dev: security@withadi.dev, an OpenPGP key, what is in scope, and what you get back. There is no bug bounty yet, and this page says why. - [ADI Store — agents, tools and dashboards you install on your own machine](https://withadi.dev/store/index.md): Agents, tools, dashboards, model backends and services for ADI, published as git repositories pinned to one commit. Installing one clones it onto your own machine. There is no account, nothing is hosted here, and nothing runs until you start it. - [Changelog tools — ADI Store](https://withadi.dev/store/changelog-tools/index.md): Turn a range of commits into release notes, and refuse a subject nobody can read. - [CRM suite — ADI Store](https://withadi.dev/store/crm-suite/index.md): A follow-up agent, its import tool, the backend it answers on, and the board that watches both. - [Code reviewer — ADI Store](https://withadi.dev/store/reviewer/index.md): Reads a diff the way a senior reviewer does, and says what would break. - [Standup board — ADI Store](https://withadi.dev/store/standup/index.md): What every agent finished yesterday, on one screen. - [Starter Status — ADI Store](https://withadi.dev/store/starter-status/index.md): The smallest complete ADI app: one panel polling one route. Install, start, read three files — the anatomy of every app.
# withadi.dev — how to report a security problem. # # RFC 9116. This file is only the address; the policy is the page it points at, # and the page is where the scope, the rules and the safe harbour are written. # # There is no bug bounty today and reports are not paid. That is said here so # nobody spends a weekend on an assumption, and said with its reason on /security. Contact: mailto:security@withadi.dev Expires: 2027-08-29T00:00:00.000Z Encryption: https://withadi.dev/.well-known/pgp-key.txt Preferred-Languages: en, ru Canonical: https://withadi.dev/.well-known/security.txt Policy: https://withadi.dev/security Acknowledgments: https://withadi.dev/security#credit # The OpenPGP fingerprint, so the key you just downloaded can be checked against # a second source rather than against itself: # # 5915 6325 8D26 58C8 A895 4A06 9A98 76BD 531B 558B # # Expires is a year out and the build refuses to ship it once it has passed # (src/integrations/security-txt.ts) — an expired security.txt reads as an # abandoned one, which is worse than not publishing it at all.