ShoalStack is now
ShoalStack is now
platform201 deploys and runs your backend from one visual graph, where you place containers, databases, gateways, and other services, connect them, and set how each one deploys.
Each service is a node on the graph, and each line between two nodes is a connection. See the whole architecture or open the settings of one service, and keep every change in the same view.
Add containers, functions, databases, queues, gateways, schedulers, or virtual machines. Place each one on the graph where it belongs.
Define routes, and map the outputs of each resource to the services connected to it. Each service then gets the configuration values it needs.
Open a node and set its source, environment variables,
ports, CPU, memory, and other options, all inside
the graph editor.
Put Markdown notes next to the related services. Record the role of each service, deployment assumptions, and decisions the team may need later.
As systems grow, background jobs, asynchronous tasks, and separate APIs add more connections. Keep these workloads visible in one architecture, so the team understands how they work together.
Schedule containers for data syncs, reports, and routine maintenance.
Connect queues to workers to run jobs without blocking API requests.
Use gateway paths to send requests to the correct backend containers.
As an example, take an API stored on GitHub that needs a database and a public gateway. Each step uses the graph for one task, from adding the first resource to opening the endpoint to traffic.
In platform201, create a project environment. Add a container to host the API, and use the graph to see where the new service fits.
Choose the GitHub repository and branch for your API, and give the build settings and environment variables the deployment needs.
Add a supported database and connect it to the API container. Map its connection details to the environment variable your code reads.
Connect a gateway to the API service, and set the public route.
Deploy the whole environment, and then check the deployment
status as it updates.
When an architecture works, use it as the start for other projects, release stages, or development tools. These capabilities extend the setup, so you do not recreate each resource.
Clone environments for staging or production without rebuilding them.
Bring an existing repository or start from a Blueprint, and explore the editor with your own setup. Build a basic environment first, and then add connected services as your application grows.
A visual infrastructure graph is a diagram of a backend system. Each node is one service or resource, such as a container, a database, or a gateway. Each line between two nodes is a connection, such as a route or a database link. The graph shows the architecture and the settings in one view, so a team does not need to piece them together from separate consoles. In platform201, the graph is also the configuration that a deployment uses.
