Built-in capability pillars (per docs grid)
| Pillar | Category |
|---|---|
| Domains | Deployment |
| Branding & SEO | Optimization |
| Users & Auth | Infrastructure |
| Payments | Commerce |
| Database | Data Management |
| Mobile | Platform Support |
| AI Gateway | AI Integration |
| Files & Media | Storage |
| Analytics | Monitoring |
| Backend | Infrastructure |
| Version Control | Development |
| Security | Protection |
These are pre-bundled — the user doesn't wire them up. "All features are built-in, ready for immediate use, and included in subscription plans."
Notable: AI Gateway
Hercules has a dedicated "AI Gateway" feature pillar. Closest analog in the vault is router.nodeops.network — a payment-aware inference router. Hercules's AI Gateway is presumably for the apps the user builds to call AI APIs without managing keys.
This is the only place in the captured set where a builder explicitly markets "the apps you build will call AI" as a first-class concern. Suggests Hercules is targeting the post-app-built user who wants their app to USE AI, not just be built BY AI. Worth a deeper look — could be a CreateOS partnership angle (Hercules-built apps could route inference + settle via MPP).
Output artifacts
- SaaS apps
- eCommerce stores
- Internal tools
- Mobile apps (with App Store / Google Play deployment claimed)
- Landing pages / marketing pages
Scalability claim
"Supports applications scaling to millions of users, page views, and revenue."
Single sentence in docs. No infra deep-dive captured.
Developer surface
- Web-based builder, prompt-driven.
- "1000+ API integrations" claimed — count, not catalog. Names not surfaced.
/docs/llms.txtreferenced — Hercules ships anllms.txtfile (Anthropic's agent-friendly docs convention). Mature docs-as-LLM-context play.- No mention of Figma import, GitHub import, or competitor migration paths.
What's NOT captured
- Tech stack details (no architecture diagram, no language choices)
- Whether the generated apps are React / Next.js / something custom
- Mobile output mechanism (native vs Expo Go vs PWA)
- Whether Hercules has a CLI or API for power users
- License / source-availability (no OSS positioning)
Versus the rest
| Capability | Hercules | Replit | Anything | Fly | Multica |
|---|---|---|---|---|---|
| Full built-in stack (auth + db + payments + hosting) | ✅ 12 pillars | ✅ Bundle | ✅ Itemized | 🟡 (sells the primitives) | ❌ |
| AI Gateway for built apps | ✅ Named pillar | 🟡 Integrations | 🟡 Integrations | ❌ | ❌ |
| Mobile output | ✅ Claimed | ✅ Native simulators | ✅ Expo Go | ❌ | ❌ |
| Open source | ❌ | ❌ | ❌ | ❌ | ✅ |
| 1000+ integrations | ✅ Claimed | ✅ "100+" | ✅ "40+" | ❌ | ❌ |
Sources
- hercules.app/docs
- hercules.app homepage