Serverless compute: read the guide
Scanned 14 Oct 2026 · Schema v5 · features v21
- From
- $29/mo
Plan fee plus per-second instance usage; Pro $29/month, Scale $299/month, Enterprise starts $1000/month
- Free tier
- No
Card required.
- Isolation
- Virtual machine
hypervisor, or nothing at all
- Regions
- 7
Frankfurt, DE · Paris, FR · Washington DC, US · AWS US East · Singapore · Tokyo, JP +1
- Capabilities
- 21 / 61
5 partial · 34 fail · 0 not assessed
- Agent readiness
- 6/11 · 10/11
read · drive, pre-login surface
Advertised for
GPU inference · Web apps apis · AI agents · MCP server hosting · Managed postgres · AI sandboxes
Built for
Developers, then technical
- · Code/container deployments, REST API/CLI/Terraform/Pulumi
- · VM isolation, CPU/GPU autoscaling and per-second billing
01 Pricing Plan fee plus per-second instance usage; Pro $29/month, Scale $299/month, Enterprise starts $1000/month
| Tier | EntryPro | Scale | TopEnterprise |
|---|---|---|---|
| Price | $29/mo + compute | $299/mo + compute | Starts $1000/month + compute |
| Includes | $10 compute credit · 10 users · 100 services · CPU concurrency 100 · GPU concurrency 20 · NVMe Volumes + Snapshots · 5 concurrent builds · 99.9% SLA · email/chat support | $100 compute credit · 50 users · 1000 services · CPU concurrency 1000 · GPU concurrency 40 · AWS Regions · private Slack channel · 99.9% SLA | $500 compute credit · unlimited users · SSO/RBAC/Audit · ISO27001 + SOC2 · custom RAM/CPU/GPU · BYOC/dedicated locations · 24×7×365 · 99.99% SLA |
Per-second instance usage; plan subscription; storage/bandwidth line items have conflicting documentation·Card required: Yes·koyeb.com
Overages: CPU nano $0.0036/hour; medium 2vCPU/2GB $0.0288/hour; GPU $0.50–$24/hour. Bandwidth/domain charging disputed by FAQ.
02 Website design Desktop public website · assessed 14 Oct 2026
Partial assessment — some pages could not be captured.
Landing uses condensed uppercase display type, a pale textured globe schematic and vivid green accents; docs switches to a restrained three-column reading layout. Pricing design could not be captured within the bounded navigation attempts.
- Technical illustration
- Landing page: captured
- Pricing: unavailable
- Docs: captured
03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.
Isolation & lifecycle
Isolation primitive
Virtual machinehypervisor, or nothing at all
Persistence
Ephemeral instance disks; testing-only public-preview persistent volumes
Snapshots / forks
Volume snapshots create new volumes; internal CPU VM memory snapshots implement Light Sleep
Resources & limits
Storage
Ephemeral SSD; preview volumes 1–10GB; Managed Postgres available
Limits & quotas
Pro 100 services/5 concurrent builds; Scale 1000 services; autoscaling and plan-dependent CPU/GPU capacity
GPU
Yes
Access
Deploy interface
git-pushcontainer-imagecliapiterraformpulumi
SDK languages
Python
Network & secrets
Egress controls
No
Secrets
Koyeb secrets — env vars / secrets injected into services
Bring your own cloud
Enterprise — BYOC / AWS regions / dedicated racks / private locations
Placement & use
Jurisdiction
FRAPARWASSINTYOaws-us-east-1SFO preview
Advertised workloads
GPU inferenceWeb apps apisAI agentsMCP server hostingManaged postgresAI sandboxes
04 Capabilities 21 pass · 5 partial · 34 fail · 61 of 61 assessed
- Supported — Documented on the public surface and verified.
- Partially supported — Exists with caveats: gated, thin, or enterprise-only.
- Not supported — Checked and not offered.
- Not assessed — Scanned before this capability was tracked. Not a lack.
Compute & storage 4/11
Persistent diskStorage that survives restart/stop (not ephemeral-only).
Partially supported
Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.
Not supported
Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).
Partially supported
Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.
Supported
Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.
Supported
GPU computeGPU-backed instances available.
Supported
Multi-regionCompute placeable in more than one geographic region.
Supported
Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).
Not supported
Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.
Not supported
Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.
Not supported
Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.
Not supported
Networking & delivery 3/9
Automatic HTTPSTLS endpoints provisioned automatically per workload.
Supported
Built-in reverse proxyPlatform routes external traffic to workload services.
Supported
Custom domainsBring-your-own domain via CNAME/DNS.
Supported
Public preview URLsShareable per-deploy / per-branch URLs.
Partially supported
Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.
Not supported
Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).
Not supported
Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.
Not supported
Email send / receiveSend and/or receive email from the workload.
Not supported
Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.
Not supported
Developer access 6/10
Public APIDocumented programmatic API.
Supported
OpenAPI specMachine-readable OpenAPI / Swagger spec published.
Supported
CLIOfficial command-line tool.
Supported
SDKOfficial client library/libraries.
Supported
SSH accessDirect SSH into workloads.
Not supported
Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.
Supported
Git deployDeploy from a Git repo / push-to-deploy.
Supported
Private container registryHosted private image registry.
Not supported
E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).
Not supported
HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.
Not supported
AI & agents 3/11
Built-in coding agentShips a first-party AI coding agent in the product.
Not supported
Agent skillsInstallable / declarable agent skills or tools.
Supported
AI app builderPrompt-to-app / vibe-coding generation surface.
Not supported
MCP serverExposes a Model Context Protocol server for agents.
Supported
MCP clientActs as an MCP client / consumes MCP tools.
Not supported
MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).
Supported
LLM gatewayRoutes LLM API calls through the platform (multi-provider).
Not supported
BYOK for LLMsBring-your-own LLM provider keys.
Not applicable
Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.
Not supported
Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).
Not supported
Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).
Not supported
Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).
Not supported
Data 1/4
First-party databasePlatform-provided managed database.
Supported
Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.
Not supported
Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.
Not supported
Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.
Not supported
Platform & operations 1/6
Scheduled tasksCron / scheduled job primitive.
Not supported
Durable workflowsDurable execution / long-running workflow primitive.
Not supported
Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).
Not supported
Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).
Supported
Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.
Not supported
Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).
Not supported
Organisation & security 3/9
Built-in authPlatform-provided authentication / IAM for workloads.
Not supported
SSO / SAMLEnterprise single sign-on.
Supported
Secrets managementFirst-class secrets storage / injection.
Supported
TeamsMulti-user team accounts.
Supported
SharingShare a running workload/resource via link (optionally gated).
Partially supported
BYOCRuns inside the customer's own cloud account.
Partially supported
Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).
Not supported
Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).
Not supported
Self-host / OSS coreOpen-source core that can be self-hosted.
Not supported
Proposed, not verified
Capabilities the scan saw but the registry does not track yet. A key is admitted only once two distinct products exhibit it. These are not scored.
- Encrypted cross-region service mesh and discoveryservice-mesh
“Service mesh supplies private connectivity and discovery; not a per-service egress firewall.” koyeb.com
05 Agent readiness Pre-login surface · counts, not a grade
Can an agent read it?
parse-ability · docs, metadata, machine-readable surfaces
6/11
5 full · 1 partial · 55% of applicable checks
- llms.txtNot supported
- llms-full.txtNot supported
- robots.txt AI policyPartially supported
- JSON-LDNot supported
- SitemapSupported
- Meta tagsSupported
- Markdown negotiationNot supported
- Content efficiencyNot supported
- Docs discoverableSupported
- Machine-readable pricingSupported
- No anti-bot wallSupported
Can an agent drive it?
act-ability · APIs, SDKs, MCP, credentials, webhooks
10/11
7 full · 3 partial · 91% of applicable checks
- Public APISupported
- OpenAPI specSupported
- MCP serverSupported
- SDK packagesPartially supported
- Auth documentedSupported
- Self-serve credentialsPartially supported
- WebhooksNot supported
- CLI toolSupported
- Error modelSupported
- Rate limits documentedPartially supported
- Agent config filesSupported
06 Coding harnesses Which agents and IDEs are documented to run here
Advertised integrations 4
- Claude Code AnthropicSupported
- Codex CLI OpenAISupported
- Cursor AnysphereSupported
- OpenCode opencodeSupported
Plausible compatibility 0
Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.
No general shell access documented, so nothing is derived. Absence is not unsupported.
07 Compliance & regions Standards held, with ordinal rigor; never a score
Certifications held 3
- ISO/IEC 27001certifiedhosted
- SOC 2 (type unspecified)certifiedhostedTYPE UNSPECIFIED on the public surface — mapped to generic soc2 (features.yml v3, rigor medium) rather than assuming the higher-rigor Type II; verify the report for the exact type.
- GDPRself-attestedhosted
Regions 7
- Frankfurt, DEfra
- Paris, FRpar
- Washington DC, USwas
- AWS US Eastaws-us-east-1
- Singaporesin
- Tokyo, JPtyo
- San Francisco, US (preview)sfo
Reference region list retained; SFO preview. Marketing 50+ locations/10 regions is not reconciled with reference; no verified 250+ edge claim.
08 Company & presence Facts only, not scored
Company
- Headquarters
- Paris area, France
- Founded
- 2021
- Team size
- 16 publicly stated
Funding
- through 2025investors · undisclosed total
- 2026-02-17acquisition · by Mistral AI
Notable people
- Yann Léger (CEO)
- Edouard Bonlieu (CPO)
- Bastien Chatelard (CTO)
Activity
Presence 6
Links found on the public surface scanned; not an exhaustive search.
09 Sources & method How this entry was produced
Public surface only
Everything here was read from koyeb.com's unauthenticated pages, docs, pricing and repository on 14 Oct 2026. Nothing behind a login was used.
Statuses, not scores
Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.
Confidence is separate
Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.
- Schema
- scan v5
- Features registry
- v21
- Keys tracked today
- 61
- Assessed on this entry
- 61
Something wrong on this page?
