ShoalStack is now
ShoalStack is now
Add your backend services to one visual platform201 graph and connect them. Deploy the environment as one version, and then read its status and its log in the deployment history.
Build the graph by hand, start from a Blueprint, or ask an assistant. The graph then holds each service, setting, and connection, and each deployment records a version with its status and log.
Place containers, databases, and gateways on one graph, and set how each one deploys.
Deploy the whole environment in one step, without manual setup in a cloud console.
Run APIs, workers, queues, and databases as one application behind a single gateway.
Attach a GitHub repository and branch to a container, or upload an archive of code.
Follow the status of each deployment version, and read the log when a build fails.
Open a ready-made graph for a common backend, change its settings, and then deploy it.
Tell the assistant what your backend needs. It adds nodes and connections to a graph.
Connect Claude, Cursor, or another MCP client to your projects, Blueprints, and graph.
Each node on the graph is one part of your backend, such as a container, a database, or a gateway. Connect the nodes, and each connection gives a service the values or the routes it needs.
Connect queues to workers, so background jobs run without blocking your API requests.
Create an account and add one service to a new environment. Follow its first version until the deployment succeeds, and add more services as your backend grows.
