- How to build and deploy Dockerfile based application
- How to build and deploy your application using Miget Buildpacks
Instance
Instance (where Application code runs) is a CloudHypervisor microVM. These are lightweight, secure virtual machines based on strong hardware virtualization. Your workloads are safely isolated no matter where they’re running on our infrastructure.
Builder
A Card on File
Creating a free resource requires a saved payment card. You are not charged for it - the card is there so we know an account belongs to a person, which is what keeps the free tier from being farmed with throwaway accounts. Add one under Settings → Payment Methods on your account, or follow the Add a card link offered while creating the resource. Either opens Polar, our payment partner, in a new tab; card details go to Polar and never reach Miget. The card belongs to your account rather than to a workspace, so it is added once and counts wherever you create a resource. One card, one free resource. A card that has already been used for a free resource cannot be used for a second one, on any account. Paid resources are unaffected - a card can pay for as many of those as you like.Limitations
- Memory Limits - The minimum allocation is 128Mi per application, making the plan suitable for lightweight applications, especially those built in memory-efficient languages like Go.
- Custom Domains - While you can add your custom domain, TLS/SSL certificates (such as Let’s Encrypt) aren’t included by default. You can, however, upload your own certificates.
- No Cron Jobs - The FREE tier doesn’t include the cronjob addon, though it can be purchased separately if needed.
- Storage - The storage available in the FREE tier isn’t optimized for high speed.
- Performance - The performance is provided on a best-effort basis. During peak times, resources may be limited, and in extreme cases, applications could be temporarily paused or stopped.
- Sleeping - An application that receives no traffic for 30 minutes is put to sleep and started again by the next request, which makes the FREE tier suited to development, testing, and projects where uptime and response time are not critical. See Sleeping below.
- Concurrent Builds - The FREE tier allows you to run one build at a time, making it suitable for smaller projects where build concurrency isn’t critical.
Sleeping
An application on the FREE tier that has not had a request for 30 minutes goes to sleep: it is scaled to zero, and the databases attached to it sleep with it. The dashboard shows it as Sleeping. The next request wakes it. That request is answered with a503 while the application starts, and the ones after it reach your application as usual. A WebSocket or server-sent events connection wakes it as well, and so does a connection to one of its databases. To wake it by hand, press Start.
A standalone PostgreSQL database on the FREE tier sleeps the same way, after 30 minutes with no client connected, and the next connection wakes it.
Paid plans never sleep. Upgrading the resource wakes everything asleep on it straight away.
Databases left asleep are deleted
When an application stays asleep for 30 days in a row, Miget reclaims what is attached to it:
A standalone PostgreSQL database follows the same schedule. Any wake resets the clock, so a single request during those 44 days keeps everything. An application with nothing attached is never deleted; it stays asleep until the next request.
The emails go to the workspace owner and admins, and they cannot be switched off.
Next steps
Compare paid plans
See what Hobby and Pro add when you outgrow the free tier.
The economics of flat-rate hosting
Why a fixed plan beats per-service billing for always-on apps.

