Platform Overview
Vercel Configuration
// vercel.json
{
"functions": {
"api/**/*.ts": {
"memory": 3008,
"maxDuration": 800,
"runtime": "nodejs20.x"
}
},
"crons": [
{
"path": "/api/crons/usage-reset",
"schedule": "0 0 1 * *"
},
{
"path": "/api/crons/subscription-check",
"schedule": "0 */6 * * *"
}
]
}Fluid Compute
Sprout uses Vercel's Fluid Compute to bypass the standard 60-second timeout limit.
Purpose
Bypass standard Vercel 60s timeout
Mechanism
Streaming + keep-alive + background processing
Limitations
- • Must stream response within 25s of first byte
- • Max 800s total execution
- • No persistent connections after completion
Use Cases
- • Long-running research tasks
- • Large file processing
- • Multi-step tool chains
Environment Variables
# Firebase FIREBASE_PROJECT_ID=hangarx-sprout FIREBASE_CLIENT_EMAIL=... FIREBASE_PRIVATE_KEY=... # AI Models KIMI_API_KEY=sk-kimi-... HUGGINGFACE_API_KEY=hf_... # External APIs TAVILY_API_KEY=tvly-... # Vercel VERCEL_URL=https://sprout.hangarx.io
Performance Metrics
< 2s
Cold Start
< 200ms
Warm Start
< 3s
First Token
+1-3s
Tool Call Overhead