Vector databases as a primitive
Native vector indexes with typed bindings, metadata filters, and one SDK path for embed, upsert, and query.
The work in flight, the work queued up, and the work we are still thinking through. Vote with your feet by joining the waitlist, or send us a request below.
Native vector indexes with typed bindings, metadata filters, and one SDK path for embed, upsert, and query.
Send and receive email from the typed runtime graph. Attachments, headers, routes, and delivery events without API key juggling.
Bring your own domain with automatic DNS guidance, certificates, and per-environment routing.
Web standard runtime with V8 isolates. Cold starts in milliseconds, not seconds.
Single-instance, stateful primitives for sessions, coordination, counters, lightweight queues, and app-level rate limits.
Neon Postgres with edge connection pooling and optional query caching at the edge.
Every push gets a stable preview URL with its own typed runtime graph.
Step-by-step, resumable workflows for long-running, retryable, and write-heavy work. Persisted and observable.
Typed file storage with signed URLs, image transforms, and per-actor scoping.
Declarative schedules attached to typed handlers. Visible in the runtime graph.
Typed config with environment scoping, audit log, and per-preview overrides.
Per-request traces across actors, databases, and workflows. Filter by user, route, or model call.
Machine-readable runtime graph for tools and coding agents to reason about your app the same way you do.
Typed pub/sub, presence, and WebSocket fan-out backed by actors.
Typed model and embedding calls with streaming, tool use, tracing, and provider routing.
Declarative auth, exposure, rate limits, CORS, and caching attached to typed endpoints.
Typed key-value storage for sessions, idempotency keys, feature flags, OAuth state, and short-lived cached data.
Deploy-time safety checks for secret leaks, unsafe primitive usage, missing auth, and RLS regressions.
Reads routed to the nearest healthy replica, writes routed to the primary, with failover-aware connection management.
Missing a primitive? Hitting a sharp edge? Tell us what you want next. We read every single one.