Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getbindu.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Let’s say

You’ve built an agent locally. It runs fine with python my_agent.py - but the moment you close the terminal, it’s gone. Nobody else can reach it, it has no public URL, and keeping it alive means keeping your laptop open. Moving an agent to the internet normally means provisioning a server, configuring networking, managing TLS, and wiring up a process supervisor. That’s a lot of infrastructure for something that should just run.

​
You want to

Run the exact same script you already have - no deploy concerns added to it - on a real public URL, with its own HTTPS domain, cryptographic identity, and persistent state. Without touching any infrastructure yourself.

​
How it works

​
The runtime model

A bindu agent’s runtime is where its Python process actually executes. By default that’s your own terminal (in-process). The bindu deploy CLI lets you run the same script elsewhere via a RuntimeProvider. The canonical provider is BoxdRuntimeProvider, which runs the agent inside a boxd microVM - isolated from your laptop, with its own public URL, DID, and HTTPS domain.

​
Your script stays clean

No deploy concerns leak into the agent script itself: 
from bindu.penguin.bindufy import bindufy

def handler(messages):
    return [{"role": "assistant", "content": messages[-1]["content"]}]

config = {
    "author": "you@example.com",
    "name": "my-agent",
    "description": "echo agent",
    "deployment": {"url": "http://0.0.0.0:3773", "expose": True},
}

bindufy(config, handler)
author is required (bindufy.py:396-401); the agent’s DID is derived from author + name.

​
Two ways to run it - same script, different verb

Locally: 
python my_agent.py        # serves on localhost:3773
On the internet: 
bindu deploy my_agent.py --runtime=boxd --auto-suspend=60
✓ my-agent serving at https://my-agent.boxd.sh
[my-agent] INFO: Started server process [12]
[my-agent] INFO: Application startup complete. Inside the VM, bindu invokes your script directly with python3 /home/boxd/app/my_agent.py (the script’s bindufy() call serves in-process, exactly as it does locally). The process is started detached via setsid nohup and its PID is tracked in /tmp/bindu-agent.pid so redeploys can stop the old process cleanly. See _start_agent in bindu/runtime/boxd_provider.py.

​
When to use each runtime

In-process (default)Boxd runtime
How to runpython my_agent.pybindu deploy --runtime=boxd
Best forLocal developmentProduction microservices
Public URLNoYes, HTTPS
Persistent stateNoYes
Multi-tenantNoYes

​
Result

A2A clients can reach the agent at https://my-agent.boxd.sh. Ctrl-C applies the configured --on-exit policy (default suspend: calls box.suspend() so the VM freezes its memory + disk and stops billing CPU). With --auto-suspend=60 passed, the VM also auto-suspends after 60 seconds of HTTP idle. Re-running bindu deploy resumes the same VM and pushes updated source. Your script never changed — only the launch verb did.

​
Current limitations (v1)

  • One runtime provider ships in-tree: boxd. The abstraction supports others (e2b, modal, fly.io) but no additional providers are bundled yet.
  • No live source-watch or auto-redeploy. Editing your script requires re-running bindu deploy.
  • No declarative manifest (bindu.toml) yet - all deploy config is via CLI flags. Planned as a follow-up.

​
Continue learning

Sunflower LogoRuntime lets you - deploy your agent to the internet.