This is what SPARKi runs on
Anyone curious about SPARKi's own production stack
The exact stack powering sparki.cleff.io and sparki-mcp.cleff.io in production
What's in the box
Every service has a transparent affiliate disclosure. Most have none.
Vercel
✓ wizardWeb frontend hosting (sparki.cleff.io)
Clerk
manualAuthentication on the chat UI
GitHub
✓ wizardSource control for all SPARKi repos
Sentry
✓ wizardError tracking across sparki-web, sparky, pico
Google Analytics 4
manualWeb traffic analytics
AWS EC2
manualSelf-hosted SPARKy MCP server (t4g.medium on sparki-mcp.cleff.io)
Pico
✓ wizardUptime monitoring (self-built, monitoring SPARKi itself + every project)
How to set it up
4 of 7 services are onboarded automatically by SPARKi's wizard. The rest you set up by following the steps below.
- 1This package is documentation-only — SPARKi already runs on this stack
- 2Use it as reference for credible '$0-ish to start' web infrastructure
Ready? SPARKi can onboard most of this for you.
Open SPARKi and run /sparki start sparki-stackfor <your-project> in a direct message. SPARKi will walk you through 4 services one at a time, verify each API key live, and write the config automatically. 3 services (Clerk, Google Analytics 4, AWS EC2) still need manual setup via vendor dashboards.