Seed App Environment

Problem

Our "agents" architecture is struggling from load on one server.

Mostly, we need to support Apps and Tools, outside the context of agents

We will repurpose the agent server to become the Seed App Environment (SAE)

It will support:

Scheduling (Triggers)

Code Execution (Tools, Runs)

App Registration + Auth

We will move to 3 machines:

SAE dev+staging

SAE prod

Docker services (web search and markdown web reads)

The app server should not allow anybody to run/execute apps. We need a permissions system, building upon the new Keyline architecture.

Probably best option: each SAE will have its own key/account/owner. That owner can grant caps in a similar way to resource grants.

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime