Teach your editor to deploy to Miget in three steps:
1. Run npx skills add migetapp/agent-skills in your project root.
2. Create an API token in the dashboard.
3. Ask Claude Code, Cursor, or Windsurf to deploy, add a database, or set up a domain.
docs.miget.com
39
Every workload on Miget runs in its own MicroVM under Cloud Hypervisor.
Your app, your worker, your database, and your preview environments are all under the same plan. They don't share a kernel.
How we isolate and monitor the platform: miget.com/blog/paas-security…
9
Every Miget account can turn on TOTP two-factor authentication.
Workspace admins can require it for every member, with a configurable grace period of up to 30 days.
If you run production on Miget, turn it on today.
miget.com/blog/two-factor-au…
2
23
Give one project its own compute resource on Miget.
POST /api/v1/projects/{project_id}/resources with a resource_id.
After that, only assigned projects can deploy to it. Any other project that tries to deploy gets a 422.
miget.com/blog/project-acces…
12
Moving a Heroku app to Miget?
Keep your Procfile. Your app still reads $PORT. Heroku Postgres moves to managed Postgres and Heroku Redis to Valkey (Redis-compatible), with tooling you already use.
Our migration guide covers each step:
docs.miget.com/migration/her…
18
Your Compose services can now share a volume. A named volume mounted by more than one service becomes a single shared storage service, and each service mounts it at its own path.
It's visible in GET /api/v1/stacks/{uuid} as volume:.
docs.miget.com/changelogs/ap…
8
Read a setting from the Miget API and write it back as is. The reads now return the names and units that the write endpoints accept: ram_size in MiB, disk_size in GiB, cpu_size. And every VPC child has its own GET.
docs.miget.com/changelogs/ap…
16
Apps on a Miget private network can now get a fixed address. Attach with static_ip: true or create the app with vpc_static_ip, and the attachment returns address_v4 and address_v6.
docs.miget.com/changelogs/ap…
17
A Postgres database on Miget grows where it runs.
Increase the CPU, RAM, and storage on the running instance.
Need failover? Go to an HA cluster of 3, 5, or 7 instances. Replication is automatic, and the connection string remains the same.
miget.com/blog/postgresql-ha…
1
11
A built site doesn't need a container, a replica, or a port.
Deploy one from GitHub, a git push, an SFTP upload, or a ZIP file. Framework detection covers 33 generators. A static site has no compute resource behind it and costs nothing, on any plan.
miget.com/blog/static-sites-…
1
17
Every Miget plan comes with a private network per region. Apps and databases on that network can find each other by name via its own DNS resolver. Nothing outside that network can reach them.
Laptop access: $29/month per VPN gateway (as of Nov 2026).
miget.com/blog/private-netwo…
21
Nine AI and developer platforms were breached in October. @wiz_io called it Black October.
We run a PaaS, so we read every public RCA. Here's the pattern and what we did about it.
Credit to @zeaburapp, @Railway, @northflank, @FireworksAI_HQ, @LightningAI, and @andromeda_ai for publishing what happened while still cleaning up. That's the only reason the rest of us can learn from it.
55
Replying to @miget_com @wiz_io
One thing to do on any platform today: put a spend limit and usage alerts on every AI key. A leaked key with a $200 cap is a bad afternoon. Without one, it's a $100k story.
Full write-up: miget.com/blog/paas-security…
22
Replying to @miget_com @wiz_io
How Miget answers them:
- every app and every build runs in its own microVM with its own kernel
- builds hold little and reach little
- tenants are isolated by default
- miget-inspector watches what workloads actually do at runtime
16
Replying to @miget_com @wiz_io
And detection failed because real credentials on real API paths don't look like an attack.
So the useful questions for any platform are:
- what runs customer code?
- what can it reach?
- what single identity can read everything?
- would anyone notice?
7
Replying to @miget_com @wiz_io
The way in: a valid long-lived credential, or the system that runs customer code (a build, an eval job).
The amplifier: one internal place that can read every tenant's secrets. One foothold becomes everyone.
5
Replying to @miget_com @wiz_io
The target was stored customer secrets. AI keys first.
A database dump needs a buyer. An AI key with no spend limit is cash the moment someone validates it. @wiz_io saw stolen keys tested within ~30 minutes, then resold.
23
