Kinesis takes about 20% of the actions required to do the same thing on a hyperscale cloud. Push a container, connect a repo, or describe what you want — and let the platform handle the non-differentiated work between you and a running URL.
Six paths in. Same runtime, same orchestration, same True-Util pricing on the other side.
Describe it. Ship it.
Prompt → Dockerfile → live URL. Maker generates a clean, auditable Dockerfile, lets you edit it, and runs it on Kinesis with one click.
Best for: prototypes · MVPs · “I just want this idea to exist”
Connect a repo. Done.
Point Kinesis at a GitHub project. We handle build, deploy, roll-forward, and the rest of the CI/CD loop. Push to ship.
Best for: teams · production workflows · continuous delivery
Bring an image from your registry.
Private or public — point us at the registry, pick a pricing model, run.
Best for: existing apps · proprietary environments · full control
Upload a Dockerfile or ZIP. We build.
Hand us the source; we build the image and run it. The clean container-native path.
Best for: reproducible builds · portability · open-source projects
Push an image file directly.
Already built locally? Upload the image and go live without setting up a registry.
Best for: quick proofs · offline builds · restricted networks
Start from a template.
Curated stacks — LLMs, vector DBs, web frameworks, batch runners. Configure and ship.
Best for: standard apps · low ops overhead · “show me the menu”
Maker writes the container, you review the container, the platform runs the container. No new framework to learn, no new YAML to memorize, no proprietary lock-in: at the end of the flow you have a standard Dockerfile you can take anywhere.
1 Prompt
Tell Maker what you want — stack, ports, dependencies, env vars, runtime behavior.
2 Dockerfile
Maker generates a clean, auditable Dockerfile. Tweak it like you would any other.
3 Run
One click to deploy. Pick True-Util Shared or Dedicated at launch.
LESS OPS SURFACE
~20% of the hyperscaler actions.
No VPC sprawl, no IAM trees, no security-group geometry. The platform handles networking, scaling, health checks, and rollbacks by default.
of the steps required
TRUE-UTIL PRICING
Pay for cycles consumed, capped at Reserved.
Bursty workloads save the most. Steady workloads pay the same as reserved would. Your bill tracks actual usage, not wall-clock time.
usage → billed
HARDWARE THAT FITS
CPU, GPU, big-iron, on-demand.
A100, H100, H200 in 1–8× configs. Multi-card for training, single for inference, Flex for batch.
PORTABLE BY CONSTRUCTION
Standard containers, nothing proprietary.
Normal Dockerfile, normal image. If Kinesis stops being the right answer, your app moves.
OBSERVABILITY BUILT IN
Logs, metrics, cost — one pane.
Real-time logs, per-app utilization, per-workload spend. No glue code, no dashboards to set up.
FOR THE ARCHITECTS
How placement actually works.
Kinesis continuously makes placement, scaling, pricing, and failure-handling decisions across a heterogeneous compute graph. Worth understanding if you care about the substrate.
Under the hood →$100 in free credit. No credit card required. Deploy your first container in under five minutes — bring a GitHub repo, a Dockerfile, or just describe what you want
