Limits and compatibility
These are current platform limits, not sizing suggestions.
Plan limits
Section titled “Plan limits”| Plan | Live apps | Invited workspace members |
|---|---|---|
| Free | 1 | 2 concurrent invited members |
| Starter | 3 | Unlimited |
| Team | 15 | Unlimited |
| Enterprise | Sized to infrastructure | Unlimited |
The workspace owner does not count toward the Free member limit. A revoked or departed member frees a seat immediately, so the two seats can be reused over time. Kyno uses workspace membership rather than per-app invitations.
Per-app limits
Section titled “Per-app limits”| Resource | Limit |
|---|---|
| Application image | 512 MB |
| Runtime memory | 512 MB |
| CPU | 1 vCPU |
| Persistent data | 1 GB |
| Processes | 64 |
| Source upload | 100 MB |
| Files in an upload | 5,000 |
| Size of one uploaded file | 50 MB |
The deploy_files MCP tool accepts at most 200 files in one call. Agents can use the file-by-file upload tools for larger projects that remain inside the platform upload limits.
Usually a good fit
Section titled “Usually a good fit”- Flask, FastAPI, or small Django apps
- Express, Fastify, or Hono
- Next.js with
output: "standalone" - Internal dashboards and approval tools
- SQLite CRUD applications
- Webhook handlers and scheduled reports
Not a good fit today
Section titled “Not a good fit today”- pandas, NumPy, or SciPy
- Playwright or Puppeteer
- Machine-learning inference
- PostgreSQL or Redis inside the application image
- Next.js without standalone output
- JVM runtimes
- Image or video processing
- High-traffic, GPU, batch, or multi-region workloads
Check the final image, not only the source size. A small repository can still produce an image larger than 512 MB.