fbuildWhere fbuild is going
A look at what's on the roadmap — team hierarchy, service flexibility, offline mode, Egos as an API, and more.
This page describes direction, not shipped features — where fbuild and Egos are headed.
Team → Workspace → Project #
A full hierarchy where a Team contains Workspaces, and each workspace contains Projects. Each workspace will get its own isolated database and its own domain (for example, yourteam.fbuild.ai).
Service flexibility #
The platform will offer sensible default providers for things like storage, queues, and email — and let you switch between alternatives as your project grows. The idea: start on the cheapest sensible default, then move between providers (for example, one database host to another) with a single click.
Online & offline #
- Offline: run against a local model, local database, and local services.
- Online: pull Egos and platform updates automatically, and send run telemetry to a central place so the system keeps improving — even when the work itself runs on your own machine.
Egos as an API #
Egos will be exposed as a versioned API (OpenAPI contract), so the console — and other tools — can drive it over a stable interface rather than being tightly coupled.
CLI ↔ UI bridge #
The command line and the UI will work together: the CLI will be able to read the panes you have open and post into them, so you can move fluidly between terminal and interface.
Install & operations #
Streamlined setup for teams — packaged for Docker / Kubernetes — so standing up your own environment is straightforward.
Have a request or want early access to any of these? Reach out through support.