Webhook capture on MicroSaaS.app
Inspect, replay and fault-inject incoming webhooks. Memory floor: 64 MB (measured floor rounded up to the next multiple of 32 MB). Status: Validated
What was measured?
- Captured every HTTP method and kept every acknowledged capture across three forced stops at 64 MB, in three consecutive rounds from fresh boots; 56 and 48 MB panicked at boot.Source: product test notes, probe date 2026-10-28, measured on the production microVM runtime. Method
| Engine | webhookd (Rust) |
|---|---|
| Category | Tooling |
| Memory floor | 64 MB |
| Status | Validated |
How long does it live?
Stateful services have a time to live of at least 1 hour, set in whole-hour steps; the default is 1 hour. The maximum depends on the plan: 4 hours on Free, 24 hours on Developer and up to 30 days on Pro. At expiry the service and its data are deleted and cannot be recovered.
What are the limits?
Needs one 50 MB storage chunk.
- Server-sent events do not stream through the platform gateway, so live tailing uses long polling.
- Replay refuses private and loopback targets by design.
A memory floor is not a sizing recommendation.
Where would it be used?
What else is in tooling?
Last updated