Frequently Asked Questions

Miget is a modern PaaS platform that allows you to host multiple applications and add-ons on a single compute resource with shared CPU and RAM, optimizing resource usage and cost efficiency.

Miget stands for Managed Infrastructure for Great Engineering Teams. The name reflects our core mission - providing a fully managed platform that empowers engineering teams of any size, so you can focus on building great software instead of managing servers, cloud primitives, and day-to-day infrastructure complexity like load balancers, TLS, autoscaling, and Kubernetes operations.

Getting started with Miget is straightforward. Simply sign up on our platform, explore its powerful features, and begin revolutionizing your development workflow with efficient, scalable, and fair resource management solutions.

No, manual configuration is not required. Miget automates platform engineering tasks, enabling you to focus on writing and deploying your code. Its automated deployment processes eliminate the usual complications associated with manual configurations.

Yes! The FREE plan starts at 0.1 CPU, 256 Mi RAM, and 1 Gi storage. You can add resources modularly: 0.25 CPU for $1.50, 512 Mi RAM for $1.50, or 5 Gi storage for $1.50. For example, upgrade to 0.6 CPU and 768 Mi RAM for just $4.50.

The Miget Fair Scheduler ensures efficient CPU resource allocation by dynamically managing allocation across your applications, guaranteeing fair distribution and optimal performance. For example, if two of your three applications are actively using CPU, they will each receive 0.25 CPU, while the third application, if idle, retains its 0.5 CPU availability.

Shared CPU means your plan's capacity comes from physical cores that are shared with other customers on the same host, so raw performance is best-effort and not guaranteed - a great fit for development, side projects, and bursty workloads. Dedicated CPU (on Professional plans) means full cores reserved exclusively for you and never contested by other tenants, for consistent, predictable production performance; you can pin entire cores to specific apps or let the Fair Scheduler distribute them across your apps. On both tiers the Fair Scheduler manages how CPU is shared across your own apps - the plan tier only determines whether the underlying cores are shared with other customers or reserved for you.

Yes, you have control over CPU allocation. You can set the CPU usage statically for critical applications while allowing other applications to share the remaining resources dynamically, ensuring high-priority workloads receive the resources they need. This means a latency-sensitive API will not be slowed down by a batch worker if you reserve resources for it.

No. The Fair Scheduler distributes CPU fairly across active services and idle services release their share back to the pool. For workloads that must never be contested, you can statically reserve CPU for critical applications, or use a Professional plan with dedicated cores.

Yes. You can run web apps, background workers, and scheduled Cronjobs together on a single plan - they all share your compute quota through the Fair Scheduler with no extra per-service billing.

You buy one fixed compute plan (CPU, RAM, and storage) and deploy unlimited apps, databases, and workers inside it. There are no per-service fees and no usage-based surprises - your monthly price is what you see on the plan. Add modular resources any time as you grow.

Managed services like PostgreSQL, MySQL, and Valkey are not billed separately - they run inside your plan's compute quota. The "catch" is simply that they consume the CPU, RAM, and storage you have already paid for, rather than adding a new line item to your bill. Most platforms charge per database; Miget bundles them into your resource allocation.

Your apps are never hit with surprise overage charges - pricing is fixed. If your services consistently need more headroom, the Fair Scheduler will keep them running within your quota on a best-effort basis, and you can add modular CPU/RAM/storage or move up a tier at any time for guaranteed capacity.

Yes. You can change your plan or adjust modular add-ons whenever you need to, and there is no long-term contract. Scale up for a launch and back down afterwards without penalty.

Yes! Miget supports both Migetpacks and Docker engine (Dockerfile) for building and deploying your applications, giving you flexibility in your development workflow. You can also deploy multi-service applications directly from a docker-compose manifest using Stacks.

Miget supports a wide range of languages through Migetpacks: Java (including Spring Boot), Node.js, Python (Django, Flask), Ruby (Rails), Go, PHP (Laravel), .NET Core, and Nginx. Migetpacks provide optimized, ready-to-use build environments - you choose the appropriate build pack, and Miget handles the rest.

Miget offers databases (MySQL, Valkey, PostgreSQL), job scheduling (Cronjobs), and scalable storage. Coming soon: MongoDB, Elasticsearch, RabbitMQ, and Kafka. We continuously expand our add-on offerings to provide you with the tools you need.

Yes. You can point custom domains at your apps on every plan, including the free tier, and Miget automatically provisions and renews free SSL certificates for them (Auto SSL). There are no certificates to manage yourself.

Every pull request can get its own full-stack preview environment with a unique URL, so you can review changes against real conditions before merging. Previews run inside your compute quota - there is no per-preview charge.

We are currently developing a CLI program called migctl to help you manage your Miget deployments and resources directly from the terminal. In the meantime you can deploy via GitHub push-to-deploy, Docker, the dashboard, the API, or an AI coding assistant.

Yes. Miget provides an open source agent skill that teaches AI coding assistants the full Miget API. Run npx skills add migetapp/agent-skills in your project and your editor (Claude Code, Cursor, Windsurf) can deploy apps, provision databases, manage environment variables, and debug deploys through natural language. See miget.com/ai-copilot for details.

Miget uses microVM-based isolation where each workload runs inside its own lightweight virtual machine with dedicated resources. This provides stronger security than typical container solutions. Our Kubernetes clusters comply with CIS benchmarks and we use FIPS 140-2 compliant cryptographic modules.

Miget's infrastructure is ISO 27001 certified and GDPR compliant, with FIPS 140-2 compliant cryptography and CIS-benchmarked Kubernetes clusters. We are not currently SOC 2 audited - if your organization requires SOC 2 or other specific attestations, contact our team to discuss your compliance requirements.

Yes. Data is encrypted in transit and at rest using FIPS 140-2 compliant cryptographic modules, and each workload is isolated in its own microVM.

Yes. Miget supports two-factor authentication, and workspace administrators can enforce 2FA for every member of the workspace, so access to your infrastructure stays protected across your whole team.

Every app you deploy is served through Cloudflare's global network, which automatically absorbs volumetric DDoS attacks before they reach your services - on every plan, with no configuration. Traffic is handled at Cloudflare's edge close to your users, and TLS is terminated there with free, auto-renewing certificates.

Scale your applications effortlessly, from one user to millions, without downtime or performance issues. Horizontal autoscaling happens inside your compute allocation, so performance goes up while your bill stays predictable.

Currently available in eu-east-1 (Warsaw) and us-east-1 (East Coast, USA). Planned regions include Frankfurt, Strasburg, London, Gravelines, Roubaix, Beauharnois, West Coast USA, Mumbai, Singapore, and Sydney.

Miget targets a 99.95% uptime SLA, backed by 24/7 support and live status reporting at status.miget.com.

Minimal. Miget runs standard containers and Migetpacks, supports plain Dockerfiles and docker-compose manifests, and is compatible with Heroku-style app.json configuration. Because you deploy the same artifacts you would run anywhere else, you can move on if you ever need to - there is no proprietary runtime to rewrite around.

Most apps move over with little or no code change - Miget's Heroku-compatible app.json and support for Docker and docker-compose mean your existing setup usually just works. Our team can also handle the move for you, migrating your apps, databases, and DNS. See miget.com/migrate to get started.

Yes. Your databases use standard engines (PostgreSQL, MySQL, Valkey), so you can export and take your data with you at any time using the same tools you already know. Your application code and container images remain yours and fully portable.