Public and private images
Deploy public images from any registry. Private images can be shared with Seemi service accounts on GitHub/GHCR, GitLab, or Docker Hub, with an access test available in the portal.
Deploy public or privately shared Linux container images with controlled networking, persistent storage, automated backups, live logs, secure terminal access, and regional placement.
Capabilities
Deploy public images from any registry. Private images can be shared with Seemi service accounts on GitHub/GHCR, GitLab, or Docker Hub, with an access test available in the portal.
Define CPU, memory, disk, ports, environment variables, secrets, commands, persistent binds, and volumes through the portal.
Schedule encrypted incremental Restic snapshots to Seemi object storage. Stateless workloads can be recreated rapidly across available nodes.
Review platform events, health, real-time application logs, restart and recreate workloads, or use a secure browser-based exec terminal.
Apply IP allowlists and optional forward authentication for compatible web workloads. Authorized users sign in through Microsoft or Google SSO.
Compatible HTTP workloads can use managed TLS and optional Cloudflare proxying for caching and additional edge protection.
Use cases
Choose a supported service from the catalog or bring a workload that fits your architecture.
How it works
Select a catalog service or define a custom container using an image reference and resource configuration.
Set ports, domains, secrets, volumes, firewall rules, forward authentication, and backup schedules.
Launch through the portal, monitor health and logs, and redeploy or restore when required.
Efficiency without compromise
Containers are not given Docker socket access or host-level privileged access that could compromise the shared platform.
For custom images, customers remain responsible for application configuration, software licensing, updates, and remediation of image vulnerabilities.
Ready to move forward?