> For the complete documentation index, see [llms.txt](/llms.txt).
> A full single-fetch corpus is available at [llms-full.txt](/llms-full.txt).
---
title: Serverless support matrix
description: Compare AGNT5 serverless runtimes, hosting targets, framework adapters, test evidence, and remaining gaps.
last_verified: 2026-07-31
---

AGNT5 serverless support is a beta execution path for workflow, function, tool, and agent components. Use this matrix to choose a tested path and understand which provider checks still belong in your release pipeline.

## Read the status labels

| Status | Meaning |
| --- | --- |
| Supported beta | The SDK or generated scaffold passes the signed AGNT5 protocol smoke for its runtime. |
| Preview | The integration passes local or container checks, but a credentialed provider deployment is not part of the default test suite. |
| Recipe | The SDK uses the framework's standard HTTP interface without adding a framework dependency. |

Provider deployment remains a separate acceptance check. A passing local smoke does not prove provider IAM, secrets, routing, timeout, or rollback configuration.

## Compare deployment targets

| Host | Runtime | Status and evidence |
| --- | --- | --- |
| Cloudflare Workers | TypeScript | Supported beta; fetch adapter and route contract smoke. |
| Vercel | TypeScript | Supported beta; Next.js route-handler smoke. |
| Vercel | Python | Supported beta; generated FastAPI entrypoint smoke. |
| Cloud Run | Python | Supported beta; generated FastAPI service smoke with `PORT` and `K_REVISION`. |
| Cloud Run | Go | Supported beta; generated `net/http` service smoke with `PORT` and `K_REVISION`. |
| AWS Lambda Web Adapter | Python | Preview; generated image build and container endpoint smoke. A deployed Lambda check is still required. |
| Generic HTTPS host | TypeScript, Python, or Go | Supported beta; one shared protocol conformance suite runs against all three SDKs. |

Use an immutable provider identifier when you run **`agnt5 serverless sync`**:

- **Cloudflare**: Worker version ID.
- **Vercel**: deployment ID.
- **Cloud Run**: revision name.
- **AWS Lambda**: published function version or container image digest.
- **Generic HTTPS**: image digest, release ID, or Git SHA.

## Compare Python frameworks

| Framework interface | Integration | Status |
| --- | --- | --- |
| Raw ASGI | Use the `ServerlessApp` returned by `serve()` as the ASGI application. | Supported beta |
| FastAPI | Call `mount_fastapi(app)`. | Supported beta |
| Starlette | Call `mount_starlette(app)`. | Supported beta |
| Raw WSGI | Use `serverless.wsgi_app` as the WSGI callable. | Supported beta |
| Flask | Call `mount_flask(app)`. | Supported beta |
| Django | Append `django_urlpatterns()` to the project URL patterns. | Supported beta |

The Python provider scaffolds generate FastAPI because it preserves the async execution model and maps directly to ASGI hosts. Flask and Django are compatibility paths for existing applications.

## Compare Go frameworks

The Go serverless handler implements the standard `net/http.Handler` interface.

| Framework | Integration | Status |
| --- | --- | --- |
| `net/http` | Pass the handler to `http.ListenAndServe` or register both protocol paths on a mux. | Supported beta |
| Chi | Register the handler with `Router.Method`. | Recipe |
| Gin | Wrap the handler with `gin.WrapH`. | Recipe |
| Echo | Wrap the handler with `echo.WrapHandler`. | Recipe |

AGNT5 does not import Gin, Chi, or Echo. This keeps the Go SDK dependency-free while preserving each application's router and middleware.

## Understand the remaining gaps

- **Lambda authentication**: AGNT5 does not sign outbound requests with AWS SigV4. A Lambda Function URL therefore needs `AuthType NONE` and AGNT5 HMAC verification. The manifest route is public.
- **Credentialed provider tests**: Cloud Run, Lambda, and Vercel Python need deployed smoke checks in an account-owned release pipeline.
- **Provider callbacks**: automatic deployment callbacks are provider-specific. Use manual **`serverless sync`** where no callback parser exists.
- **Batch policies**: aggregate batch enforcement is not available for serverless endpoints during beta.
- **Provider limits**: cold starts, maximum duration, payload size, and concurrency remain provider constraints.

## Run the checked-in tests

```bash
just test-e2e-workerless-conformance
just test-e2e-workerless-cloud-run-smoke
just test-e2e-workerless-python-provider-smoke
just test-e2e-workerless-python-provider-smoke 1
```

The final command enables the Lambda Docker image build and container smoke.

## Next steps

- [Serverless endpoints](/docs/run/serverless-endpoints.md): follow the deployment lifecycle and protocol boundary.
- [Deploy to Cloud Run](/docs/integrations/cloud-run-serverless.md): generate and deploy a Python or Go service.
- [Deploy to AWS Lambda](/docs/integrations/aws-lambda-serverless.md): build the Web Adapter image and configure a Function URL.
- [Integrate Python web frameworks](/docs/integrations/python-web-frameworks.md): mount AGNT5 in FastAPI, Starlette, Flask, Django, ASGI, or WSGI.
- [Build a serverless endpoint in Go](/docs/integrations/go-serverless.md): register components and connect a Go HTTP router.