Plans

The Plans section is where you manage your app's resources. This is how you scale up when traffic increases, downsize when you want to save money, or adjust your hosting tier based on what your app actually needs.

Current Configuration

At the top, you'll see your current setup: which region your app is deployed to, your current container size, and your current domain. This is a quick reference showing what's live right now.

Choosing Your Plan

Galaxy offers different plans for different needs. Each plan supports different container sizes and features:

Free or Sandbox Plans: Great for testing and learning. Limited resources, lower cost (or free). Perfect for staging environments and early development.

Production Plans: For apps with real traffic. Multiple container sizes available, better resource allocation, and features you need for production workloads.

Business Plans (coming soon): Enterprise-grade with custom features.

Pick the plan that matches your app's current needs. You can always change later as your app grows.

Container Sizing

Once you pick a plan, select your container size. Container size determines how much RAM and CPU your app gets. Bigger containers handle more traffic and heavier workloads, but cost more to run.

The container size table shows everything you need to decide:

Size name: Tiny, Compact, Standard, Double, etc.
Memory: RAM allocated to each container
CPU: Processing power
Hourly price: What it costs per hour
Monthly estimate: Rough cost if running 24/7 for a month

How to Choose a Container Size

Starting out? Pick a smaller container (Compact or Small) and scale up if you hit limits. Most apps do fine starting smaller.

Existing app? Look at your current resource usage. If your containers are always at high CPU or memory, upgrade to the next size. If they're idle, you might be paying for more than you need.

Performance issues? Try upgrading to the next container size. See if it helps. If it does, that's your bottleneck. If it doesn't, the issue is elsewhere (code optimization, database queries, etc.).

Test different container sizes and watch your app's performance. You'll find the sweet spot where cost and performance balance nicely.

Container Count

Most apps run one container. But you can run multiple containers if your app gets heavy traffic or needs redundancy.

Each additional container is charged separately. Running two Standard containers costs twice as much as running one. But you get better performance and fault tolerance.

Single vs Multiple Containers

Single container: Simple, cheaper. Fine for low to moderate traffic. If that one container crashes, your app goes down until it restarts.

Multiple containers: More resilient. Galaxy distributes traffic across all containers. If one crashes, others keep handling requests. Better performance under load.

For production apps, at least two containers is recommended. For mission-critical apps, three or more is better. This gives you redundancy and better performance.

High-Availability

If you're running a Standard (1GB) container or larger with three or more containers, high-availability is automatically enabled. This distributes your containers across different availability zones.

See the Overview page for details on high-availability.

Changing Your Plan or Container Size

Ready to scale? It's simple:

Open your app and navigate to Plans
Select your new plan (if changing tiers)
Pick your new container size
Adjust container count if needed
Click Apply

Galaxy applies the change and triggers your next deployment. Your app doesn't go down. The change takes effect when your app restarts.

Scaling is instant for most changes. Want to test a bigger container? Change it here and test. If it doesn't help, change back. No harm in experimenting.

Downscaling to Save Money

Running more containers than you need? Or paying for bigger containers than necessary?

Downscaling is just as easy as scaling up:

Go to Plans
Reduce container size or count
Click Apply

Your app updates and triggers the next deployment. Your monthly bill decreases immediately.

For temporary cost savings, you can also Stop your app from the Overview page. Stopped apps don't cost anything, but users can't access them until you restart.

Different Plans for Different App Types

Different app types (Meteor, Node.js, Python, AdonisJS) have different plan names and container options. The concept is the same: pick a tier, choose a size. But specific options vary by runtime.

Check our billing documentation for details specific to what you're running.

Cost Estimation

The table shows hourly and monthly costs. Monthly estimates assume 24/7 running (720 hours in a month).

Not running 24/7? Adjust the estimate in your head. Running only during business hours? That's roughly 8/24 of the daily cost. Running only weekdays? That's roughly 5/7 of the weekly cost.

Galaxy charges by the minute, so you only pay for time your app actually runs.

Estimating costs can be tricky. When in doubt, go with the larger estimate. It's better to be surprised that costs are lower, not higher.

Auto-Scaling

Some plans support auto-scaling. This automatically adjusts container count based on traffic. High traffic? Automatically add containers. Traffic drops? Automatically remove them.

If your plan supports auto-scaling, you can configure it here. You set minimum and maximum container counts, and Galaxy handles the rest.

This is perfect for apps with variable traffic. You don't pay for containers you're not using, but you always have enough capacity when traffic spikes.