Core concepts
The few things you need to know to use Pyo.
Teams
Everything in Pyo belongs to a team. Invite people as owners, admins, developers or viewers. See Inviting your team.
Projects
A project groups related services, like a website with its API and database. Services in a project share a Kubernetes namespaceA named area inside a cluster that keeps one project's services and settings apart from everything else., so they can reach each other by name.
New projects are isolated: other projects' services can't reach them.
Services
A service is one thing you run, like a website, an API, a database or a background worker. It comes from a Git repository, a container imageA packaged, ready-to-run copy of a program and everything it needs. Pyo builds one from your code or pulls an existing one. or a template.
Deployments
A deployment is one build and rollout of a service. Pyo keeps the history, so you can see what ran when and go back to an earlier version.
Clusters and servers
A cluster is a group of servers running k3sA lightweight version of Kubernetes, the standard system for running containers across servers. Pyo sets it up for you.. A team can have several, for example production and staging. Each cluster runs an agent that connects out to Pyo, so you don't have to open anything on the server for Pyo to reach it. See how Pyo fits together.
Replicas
A replica is one running copy of a service. More replicas handle more traffic, and they can run on different servers. See Scaling a service.