Q-Lambda
Event-driven compute, but the events are also probabilistic.
Q-Lambda runs your function in response to an event. Or in response to a different event. Or in response to no event, just based on prior probability that something must have happened.
Capabilities
What it does. Or appears to do.
/feature/01
Up to 10GB memory
Allocated, but not necessarily yours.
/feature/02
15-minute max runtime
Functions exceeding 15 minutes are presumed to have completed and billed accordingly.
/feature/03
150+ runtimes
Including Python, Node, and a runtime called 'Spirit' that we cannot demonstrate.
/feature/04
Cold starts
Our cold starts are warm starts in 49% of timelines, which we round up.
Spec sheet
By the numbers (unverified).
| Concurrency | 1,000 (soft) · ∞ (hard) |
| Pricing unit | $ per GB-second-maybe |
| P99 cold start | 200ms · also 11 minutes |
| Free tier | 1M invocations, in select universes |
| Pricing | From $0.0000002 per invocation-maybe. |
Customer outcomes
Statements made by people, allegedly.
“We replaced our cron jobs with Q-Lambda. The reports now arrive when finance least expects them, which is the point.”
R. Holloway
CPO · OmniCorp
Frequently entangled questions
Things people have asked, in some branch.
Does it actually run my code?+
Yes, in some interpretations of yes.
How do I debug it?+
You don't. You wait.
◇ Ready to deploy?
Bring Q-Lambda into your stack.
Or don't. The product will continue to exist either way, in some form, somewhere.