crashlabs/huskies
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 26 Wiki Activity

storkit: create 407_spike_fly_io_machines_for_multi_tenant_storkit_saas

Browse Source
This commit is contained in:
dave
2026-03-26 21:01:42 +00:00
parent e6b300e70e
commit 8998dac593
1 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.storkit/work/1_backlog/407_spike_fly_io_machines_for_multi_tenant_storkit_saas.md
+10 -3
View File
@@ -10,15 +10,22 @@ Can Fly.io Machines provide sufficient isolation, fast enough cold start, and si
## Hypothesis ## Hypothesis
- TBD Fly.io Machines (Firecracker-based microVMs) offer the right balance of isolation, cold-start speed, and operational simplicity for early-stage SaaS. A thin Rust auth proxy routes JWT-authenticated requests to per-tenant machines, avoiding the ops complexity of self-managed gVisor/Kubernetes.
## Timebox ## Timebox
- TBD 4 hours
## Investigation Plan ## Investigation Plan
- TBD - [ ] Review Fly.io Machines API — create/start/stop/destroy machine via REST, assess Rust `reqwest` integration
- [ ] Assess isolation model — Firecracker microVM vs gVisor; is it sufficient for tenants running arbitrary shell commands via claude code?
- [ ] Test cold start time for a storkit container image (target: <2s)
- [ ] Evaluate persistent volume support — can a volume be attached per tenant for `.storkit/` and project root?
- [ ] Assess Claude auth injection — how to securely pass `~/.claude/.credentials.json` per tenant at machine start
- [ ] Sketch the auth proxy design — JWT validation → machine lookup → reverse proxy (WebSocket support required)
- [ ] Check pricing model for always-on vs stop-on-idle machines at small tenant counts (10, 100, 1000)
- [ ] Identify any showstoppers (network egress limits, image registry, machine count limits per org)
## Findings ## Findings