Functions

Deploy backend logic from agent workspaces.

Let agents create, deploy, invoke, and inspect JavaScript functions for APIs, webhooks, data transformations, scheduled jobs, and product automation.

Start now

Fully managed

Create backend logic from the same workspace where agents write, test, and deploy code.

Global invocation

Expose APIs, webhooks, transformations, and automation handlers that run on demand.

Connected resources

Bind functions to databases, auth, secrets, web apps, and agent runtimes.

Secure by default

Keep credentials out of code and control access through managed project resources.

What you can build with Functions

View all examples

Hello world

Return a JSON response from the smallest possible deployable function.

View example

Contact form to database

Validate a form submission and store it in a connected Computer Agents database.

View example

Signed webhook handler

Verify incoming webhooks with a signing secret from a connected Secrets vault.

View example

Trigger an agent run

Expose an API endpoint that starts a connected Agent Runtime for async work.

View example

Pricing

Functions are the lightest backend surface for bursty APIs, webhooks, jobs, and automation.

Function pricing in Compute Tokens
Active execution	0.1 CT / active execution minute Billed while the function is actively handling work.
Idle function	No idle runtime charge A deployed function can stay available without the continuous runtime rate of a web app or agent runtime.
Connected resources	Normal resource usage applies Databases, auth modules, computers, agent runtimes, and other bound resources keep their own pricing model.

SDK functionality

The JavaScript and Python SDKs expose the full function lifecycle: creation, deployment, rollback, invocation, analytics, logs, bindings, files, runtime inspection, and secrets. Deployed Node functions can also import computer-agents/runtime/server for runtime access to bound resources.

SDK functionality
Lifecycle	Create, list, get, update, and delete the resource through the product manager or the generic resources manager.
Deployments	Deploy, list deployment history, and roll back to a previous deployment from JavaScript or Python.
Invocation	Invoke live routes directly from the SDK for health checks, smoke tests, backend calls, and CI workflows.
Operations	Read analytics, request logs, runtime logs, runtime config, and deployed runtime state from one resource surface.
Bindings	List, create, update, and remove bindings to databases, auth modules, secrets, web apps, functions, and runtimes.
Files	List, read, write, upload, download, and delete files that belong to the deployed resource.
Secrets	List, create, read, update, and delete secrets scoped to the resource without checking values into source files.

Read bound resources inside a function

How to set it up

Start from the workflow that fits the job: script infrastructure with the SDK, operate directly in Develop, or ask an agent to create the function from project context.

Via SDK

Create, deploy, invoke, inspect, and bind functions from JavaScript or Python when infrastructure should be scripted.

On the platform

Create a Function resource in Develop, choose the source computer and folder, bind resources, and deploy from the UI.

By agent

Ask a project agent to write the function, connect the required resources, deploy it, test it, and document the endpoint.

1. Create the function handler

2. Upload the code to a computer

3. Create, deploy, and invoke the function

How to deploy

A deployment turns source code in a computer or project workspace into a callable backend resource that can use the rest of the project.

How to deploy
Prepare the handler	Create a small endpoint with a health path, predictable inputs, and a clear response contract.
Create the resource	Point the function at a source computer, source folder, and nodejs22 runtime.
Bind dependencies	Attach the database, auth module, secret store, web app, or agent runtime the function needs.
Deploy and test	Deploy the function, invoke the health route, and run a representative payload before connecting traffic.
Document the contract	Record the endpoint, required bindings, expected payloads, and operational owner inside the project.

How to manage

Functions are operational resources, not snippets. Keep status, logs, analytics, files, bindings, and runtime configuration visible so production behavior is easy to understand.

How to manage
Analytics	Track request volume, errors, and active execution patterns so function behavior is visible over time.
Logs	Use request and runtime logs to debug payloads, dependency failures, and external API issues.
Runtime state	Inspect runtime configuration and files when a function was generated or modified by an agent.
Bindings	Review connected databases, auth modules, secrets, and upstream apps before making changes.
Smoke tests	Use SDK invocation after deployment and after every significant source change.

Inspect production behavior