The official website for OpenAdapt.AI, the governed compiler for repeated GUI workflows.
Lifecycle: Beta. The website documents the evidence-bounded browser product, partner-scoped desktop and RDP qualification, and the real-environment gate for Citrix. Availability and evidence state are reported separately. This label is not a statement that every described deployment path or target application is production-ready.
This is the Next.js-based landing page for OpenAdapt, featuring:
- Canonical product truth centred on deterministic compiled replay
- Audience paths for developers, automation teams, and regulated enterprises
- Execution paths for local, managed browser, and customer-controlled operation
- Industries grid showing use cases across different sectors
- Developer resources and contribution information
- Email signup for product and launch updates
- Single-page contact + booking flow on landing (
#book) - Booking page for intro calls (
/book) - Contact intake form for sales workflows (
/contact)
- Next.js 14 - React framework
- Tailwind CSS + DaisyUI - Styling
- Framer Motion - Animations
- Netlify - Hosting and forms
# Install dependencies
npm install
# Run development server
npm run devOpen http://localhost:3000 to view the site.
Booking is code-owned and always routes to the canonical Cal.com event:
https://cal.com/richard-abrich/30min?overlayCalendar=true
Deploy-time booking-provider overrides are intentionally ignored so stale
environment variables cannot redirect the homepage form or /book embed.
The site is automatically deployed to Netlify on push to the main branch.
- Production: openadapt.ai
| Repository | Description |
|---|---|
| openadapt-flow | Canonical engine: compiler, governed runtime, validation, and limits |
| OpenAdapt | Installer and unified CLI that routes openadapt flow to the engine |
| openadapt-desktop | Desktop authoring and operator surface, in development |
| openadapt-evals | Evaluation and benchmark research |
| openadapt-privacy | Optional PII/PHI scrubbing library |
The public product story must not treat repository count as product breadth. Research and internal tools belong in reference material, not top-level positioning.
MIT - see LICENSE for details.