This is something we support as well. You're correct that most of our documentation (including quickstarts) focuses primarily on web-facing apps.
Our current modules support running Python jobs using Fargate/ECS and Lambda (using Docker containers or packaged zip files).
Today, it is possible to pause workloads by destroying the app (nullstone down --app=<app>). Obviously, that's not ideal and we do have plans to support pausing workloads to reduce costs.
We support auto build/deploy upon the launch of your application and then on every code commit to the branch configured. The docker image is stored in a container registry in your cloud account.
Outside of the auto build/deploy process, we don't yet support ad-hoc docker builds.
Our current modules support running Python jobs using Fargate/ECS and Lambda (using Docker containers or packaged zip files).
Today, it is possible to pause workloads by destroying the app (nullstone down --app=<app>). Obviously, that's not ideal and we do have plans to support pausing workloads to reduce costs.