STARM Launchpad
Turn a container image into a reviewable deployment configuration. Choose resource limits, health checks and exposure settings, then export standard YAML.
image: "nginx:alpine"
ports: ["127.0.0.1:8080:80"]
cpus: 0.5
mem_limit: "256m"Make the decisions between your image and your infrastructure clearer. Build deployment configurations. Plan network boundaries. Keep the output yours.
Two working tools. Free to use. No account required.
# Generated by STARM Launchpad. Review before deployment.
name: "web"
services:
"web":
image: "nginx:alpine"
restart: unless-stopped
init: true
ports:
- "127.0.0.1:8080:80"
cpus: 0.5
mem_limit: "256m"
pids_limit: 256
security_opt:
- no-new-privileges:true
environment:
"APP_ENV": "production"
healthcheck:
test:
- CMD
- wget
- -q
- --spider
- "http://127.0.0.1:80/"
interval: 30s
timeout: 5s
retries: 3
start_period: 20s
logging:
driver: json-file
options:
max-size: "10m"
max-file: "3"
networks:
- app
networks:
app:
driver: bridge
Focused tools for engineers working across containers and networks. Open them, use them, take the result into your own workflow.
Turn a container image into a reviewable deployment configuration. Choose resource limits, health checks and exposure settings, then export standard YAML.
image: "nginx:alpine"
ports: ["127.0.0.1:8080:80"]
cpus: 0.5
mem_limit: "256m"Plan IPv4 address space before changing a network. Calculate ranges, split subnets and check overlap between application, container and service networks.
Export standard Compose or Kubernetes YAML. Put it in version control, review it in a pull request and deploy with your existing tools.
Resource limits, local port binding and health settings appear in the output. Image compatibility and production assumptions stay visible.
Configuration and subnet calculations run on your device. No account, cluster credentials or configuration upload is needed.
We focus on the preparation work that makes application delivery easier to understand and repeat.
Read the getting started guideStart with the container image, listening port and resource budget. Choose Compose for a single host or Kubernetes for a cluster.
Choose port exposure and health checks. Use Netkit to compare the CIDR ranges you plan to use for your network.
Download the files, validate them against your environment and apply them with Docker or kubectl on infrastructure you control.
The first release is a foundation. Next, we want to connect application blueprints, configuration review and network troubleshooting.
Compose and Kubernetes generators, IPv4 subnet calculations, overlap checks and downloadable outputs.
Templates for app, database and reverse proxy stacks, with explicit storage and service dependencies.
Configuration comparisons, preflight checks and guided network diagnostics for container workflows.
A useful first step, in your browser. No account required.