Deploying applications to production should be simple. With Out Plane, you can go from code to a live, scalable application in under five minutes. This guide walks you through every step of deploying your first application.
What You'll Learn
By the end of this tutorial, you will:
- Connect your GitHub account and select a repository
- Configure your application's build settings and resources
- Deploy and monitor your application in real-time
- Access your live application with a public URL
Prerequisites
Before you begin, make sure you have:
- A GitHub account with at least one repository containing your application code
- Your application code in a deployable state (with a Dockerfile or using a supported framework)
Out Plane supports all major frameworks including Next.js, Django, FastAPI, Express, Rails, Go, and more. If your project has a Dockerfile or uses a common framework, you're ready to deploy.
Step 1: Create Your Out Plane Account
Out Plane uses GitHub for authentication. This means no separate password to remember, and your repositories are instantly accessible.
- Navigate to console.outplane.com
- Click Continue with GitHub
- Authorize Out Plane to access your GitHub account
- Once authenticated, you'll be redirected to create your first application
Starter and Pro plans both begin with a 14-day free trial, so you can deploy and test before the first monthly charge.
Step 2: Select Your Source Code
Out Plane offers two ways to connect your code:
Option A: Git Provider (Recommended)
This option gives you the best experience with automatic deployments on every push.
- Your connected GitHub repositories appear in a searchable list
- Use the search bar to find your repository
- Click to select the repository you want to deploy
Both public and private repositories are supported. Private repositories require GitHub authorization, which you've already granted during signup.
Option B: Public Repository URL
If you want to deploy a public repository without connecting your full GitHub account:
- Switch to the Public Repository tab
- Paste the full GitHub URL (e.g.,
https://github.com/username/repo) - Continue to configuration
Step 3: Configure Your Application
After selecting your repository, you'll configure how Out Plane builds and runs your application.
Application Name
Out Plane automatically generates a unique name based on your repository name. You can customize this if you prefer a different identifier. This name becomes part of your deployment URL.
Build Method
Choose how Out Plane should build your application:
Buildpacks (Default) - Best for most applications. Auto-detects language and framework, builds without configuration.
Dockerfile - Best for custom builds. Uses your Dockerfile for complete build control.
Buildpacks are recommended for most projects. Out Plane uses Paketo Buildpacks to automatically detect your application's language and dependencies. Supported languages include Node.js, Python, Go, Java, Ruby, PHP, .NET, and more.
If your project has specific build requirements, use a Dockerfile for full control over the build process.
Port Configuration
Specify the port your application listens on. Common defaults:
- Node.js/Express:
3000 - Django/FastAPI:
8000 - Go:
8080 - Next.js:
3000
If unsure, check your application's startup configuration or framework documentation.
Branch Selection
Out Plane fetches available branches from your repository. Select the branch you want to deploy:
- main or master for production deployments
- Feature branches for preview environments
The selected branch determines which code version deploys. Future commits to this branch can trigger automatic redeployments.
Root Directory
For monorepos or projects where your application code isn't at the repository root:
- Click Browse to open the file explorer
- Navigate to the directory containing your application
- Select the folder (e.g.,
/apps/backendor/packages/web)
Leave as ./ if your application code is at the repository root.
Instance Count
Configure how many instances run your application:
- Instances: Number of copies kept running (default: 1)
- Plan ceiling: The highest number you can set (Starter 1, Pro 5, Growth 10)
You set the instance count yourself and change it whenever you need to. Every instance stays up, so the first request after a quiet period never waits for a cold start.
For development or low-traffic applications, 1 instance is sufficient. For production workloads expecting traffic variability, consider 2 to 3 instances for redundancy.
Region
Out Plane runs in one place, and there is nothing to pick here:
Region:
- Nuremberg, Germany - Every application and database, on every plan
Your code and your data stay in Germany, which makes EU data residency the default rather than a setting somebody has to get right.
Instance Type
Select the compute resources for your application. Out Plane offers a range of instance types from lightweight development instances to high-performance enterprise options.
The smallest instance is enough for development and testing, and its usage fits inside the allowance included with your plan. For production workloads, choose an instance type based on your application's CPU and memory requirements.
You can start small and resize anytime without changing your application code.
Step 4: Add Environment Variables
Most applications require configuration through environment variables. Out Plane provides two ways to add them:
Using the Form
- Click Add to create a new variable
- Enter the Key (e.g.,
DATABASE_URL,API_KEY) - Enter the Value
- Repeat for each variable
Values are masked by default. Click the eye icon to reveal them.
Using Raw Edit
For bulk entry or pasting from a .env file:
- Click Raw Edit
- Paste your variables in
KEY=valueformat, one per line - Click Apply
DATABASE_URL=postgres://user:pass@host/db
REDIS_URL=redis://localhost:6379
API_KEY=your-secret-key
NODE_ENV=production
Environment Scoping
Each variable can apply to specific environments:
- Development: Used during development builds
- Preview: Used for branch preview deployments
- Production: Used for production deployments
Select at least one environment per variable. Most variables should apply to all three.
Step 5: Deploy Your Application
With configuration complete, click Deploy Application.
Deployment Pipeline
Your deployment progresses through these stages:
- Queued: Waiting for build resources
- Building: Compiling code, installing dependencies
- Deploying: Rolling the new version out to your instances
- Ready: Application is live and accepting traffic
Watch the build logs in real-time to monitor progress. Most deployments complete in 1-3 minutes depending on your application's complexity.
Deployment Success
When deployment completes, you'll see:
- Status badge showing Ready
- Your live URL:
https://your-app-name.outplane.app - Deployment duration and timestamp
Click the URL to view your live application. SSL certificates are automatically provisioned.
Step 6: Monitor Your Application
After deployment, Out Plane provides comprehensive monitoring tools.
Runtime Logs
Access your application's logs in real-time:
- Navigate to your application
- Click Logs in the sidebar
- Filter by severity: Error, Warning, Info, Debug, Trace
Use the time range selector to view historical logs (up to 7 days).
Metrics Dashboard
Monitor your application's resource usage:
- CPU Usage: Processing utilization per instance
- Memory Usage: RAM consumption
- Network: Ingress and egress traffic
- Disk I/O: Read and write operations
Access metrics via Observability > Metrics in the sidebar.
HTTP Request Logs
Track all incoming HTTP requests:
- Filter by status code (2xx, 3xx, 4xx, 5xx)
- Filter by HTTP method (GET, POST, PUT, DELETE)
- View response times and request paths
Next Steps
You've deployed your first application on Out Plane. Here's what to explore next:
Add a Custom Domain
Replace your-app.outplane.app with your own domain:
- Go to Domains in the sidebar
- Click Map Domain
- Enter your domain (e.g.,
app.yourdomain.com) - Configure DNS records at your registrar
Connect a Database
Out Plane provides managed PostgreSQL databases:
- Navigate to Databases
- Click Create Database
- Select your PostgreSQL version and size
- Use the connection URL in your application's environment variables
Set Up Auto-Deployments
Enable automatic deployments when you push to your branch:
- Go to Settings > Build
- Verify your branch configuration
- Push code to trigger automatic deployment
Troubleshooting
Build Failures
If your build fails:
- Check the build logs for specific error messages
- Verify your Dockerfile or framework configuration
- Ensure all dependencies are specified in your package manager
- Confirm the correct port is configured
Application Not Starting
If your application builds but doesn't start:
- Check runtime logs for startup errors
- Verify environment variables are correctly set
- Confirm the port matches your application's configuration
- Check health endpoints if configured
Need Help?
- Visit our documentation for detailed guides
- Join our Discord community for support
- Contact us at [email protected]
Summary
Deploying to Out Plane involves five straightforward steps:
- Connect your GitHub account
- Select your repository
- Configure build settings, resources, and environment
- Deploy and monitor the build process
- Access your live application
With transparent pricing metered by the minute, an instance count you control, and built-in monitoring, Out Plane handles your infrastructure so you can focus on building great products.
Ready to deploy? Get started with Out Plane and open a 14-day free trial.



