Skip to main content

​
Pods

A pod is a persistent Linux container running on InstaPods infrastructure. Pods are full system containers — all files, installed packages, and configurations survive restarts. Think of it as your own tiny server. Each pod gets:
  • A public URL (e.g., my-app.nbg1-1.instapods.app)
  • A dedicated SSH port for remote access
  • A pre-installed development stack based on its preset
  • Its own filesystem at /home/instapod/app
Pods can be started, stopped, restarted, resized, and deleted. When stopped, your data is preserved — you only lose the running processes.

​
Presets

A preset defines the software stack pre-installed in a pod. InstaPods offers five presets: Presets use pre-built images, so pod creation takes just 1-2 seconds. See Presets Overview for details on each.

​
Plans

Plans determine the resources allocated to your pod: All plans include SSH access, custom domains, automatic SSL, and the web IDE.
The Launch plan does not support database services (MySQL, PostgreSQL, Redis). Upgrade to Build or higher to install services.

​
Regions

A region is a geographic location where your pods run. Each region has one or more servers. When creating a pod, you can optionally select a region — if you don’t, InstaPods automatically picks the closest server based on your location. List available regions via the CLI or API:
This shows each region and how many servers are available. You can also view regions at app.instapods.com or via the API at GET /api/regions.

​
Teams

A team is the organizational unit for billing and access control. Every user belongs to at least one team.
  • Pods belong to teams, not individual users
  • Billing (subscriptions, invoices) is per-team
  • Team members can manage all pods within the team
  • You can create multiple teams and switch between them
See Teams for more on managing teams and inviting members.