inTake is a self-hosted platform for deploying and managing applications — similar to Vercel, Railway, or Heroku — but with full control over your infrastructure and data. It provides automated deployment workflows, container orchestration, and infrastructure management tools, all within your private environment.
This guide will walk you through setting up and running your own self-hosted instance of inTake.
Prefer not to self-host? Try inTake Cloud for a fully managed experience.
Make sure you have the following:
- Docker installed
- A Tailscale account
- A domain name
- A server (recommended: 2 vCPUs, 8GB RAM)
Run the following command to begin setup. It will guide you through configuring everything needed for your inTake instance:
curl -fsSL https://get.gointake.ca | bashinTake uses Tailscale for Zero Trust networking — enabling secure SSH and internal communication via your private tailnet.
You'll be prompted to enter:
-
Tailnet name Found in the header after logging into Tailscale, e.g.,
johndoe.github -
Auth Key Create one under Settings > Personal > Keys. Enable
ReusableandEphemeral. -
OAuth Client Key Go to Settings > Tailnet > OAuth clients. Enable all
readscopes andwriteforAuth Keys, then create the key.
inTake uses Traefik as a reverse proxy. The email you provide will be used to generate SSL certificates for your domain.
You’ll be asked to:
Enter your email for SSL certificate generation
>Enable custom domain support for your services:
-
Add a DNS A record:
- Type: A
- Name:
*.up - Value:
<your-server-ip> - Proxy: OFF
-
When prompted, enter your domain, e.g.,
up.johndoe.com
inTake uses Payload CMS under the hood. A JWT secret is required for:
- Authentication
- Encrypting sensitive data like environment variables
⚠️ Use a strong, persistent secret. Do not change this between deployments.
When prompted:
Enter your JWT secret (keep it safe and consistent)
>Once all configuration steps are complete, the necessary files will be generated. Follow the remaining prompts in your terminal to launch your instance of inTake.
Thanks to all who have contributed to inTake!