You push, your VPS updates itself

Here's what it looks like in the panel

A complete deploy pipeline, no YAML

The convenience of a Vercel-style platform, on a server that's yours.

• Link the repo from the panel: You pick a repository from your GitHub account, the branch and a project name. The branch is checked to exist before the deploy is created.
• Automatic webhook: The webhook is created for you on GitHub, with SSL verification. There's nothing to touch in the repository settings.
• Pull on every push: Every push to the tracked branch triggers a git pull on the VPS. Pushes to other branches are ignored.
• Scripts before and after: A pre-pull script (which discards local changes by default) and a post-pull one to install dependencies, build or restart services.
• Visible status: Cloning, pulling, building, restarting, online, or error with the message. You know where each deploy stands.
• Commit history: Every commit received is recorded with its SHA, message, author, date and the files added, deleted and modified, with a link to GitHub.
• Manual redeploy: Deploy again with a button when you need to, without making an empty commit.
• The whole app in one place: You associate the repo's domains, systemd services and scheduled tasks with it, and see the whole application together.
• Several branches, one VPS: The same repo can be deployed on different branches within the same VPS: production and staging side by side.
• No YAML to maintain: There's no pipeline file to break when the syntax changes. Two shell scripts, which is what ends up running anyway.
• No build minutes: The build runs on your VPS. No minute quota and no runner queue: the limit is the CPU you're already paying for.

Your first deploy in minutes

1. Connect your GitHub account: Once, from the panel.
2. Pick a repo and a branch: The code is cloned onto the VPS and the webhook is created for you.
3. Define build and restart: For example npm ci && npm run build, and restarting your service.
4. Publish it with a domain: You assign a domain with HTTPS and every push updates it.
5. Check the history: Every deployed commit is kept with its SHA, author, message and changed files. If something broke, you know exactly with what.

How it works underneath, and what to keep in mind

• There's no runner and no CI agent: the GitHub webhook notifies the VPS and the VPS runs git pull on the clone it already has. That's why a deploy takes as long as your build and nothing more.
• The pre-pull script discards local changes by default. That's on purpose: a file edited by hand on the server is the most common reason a pull fails in the middle of a deploy.
• The post-pull script is where everything of yours goes: installing dependencies, building, migrating the database, restarting your app's systemd service.
• Pushes to other branches are ignored. The same repository can be deployed on different branches within the same VPS, so production and staging coexist without stepping on each other.
• Each repository-and-branch combination is deployed once per VPS.
• It needs systemd running on the VPS. It's verified in production on Ubuntu 22.04 and compatible with 18.04, 20.04, 24.04 and 26.04; it isn't available on 16.04, because systemd 229 won't start on a host running cgroup v2.
• You need the GitHub account linked with a valid token. If the token expired right as you deleted a deploy, the webhook can be left hanging on GitHub and you have to delete it by hand.
• The build runs on the VPS and uses its memory. On the smallest plan, keep the repository light: building something big runs out of memory halfway through.
• Company administrators edit and delete deploys; members can view and create them.
• Real root over SSH: the panel is a shortcut, not a cage. Anything it does with a button, you can also do by hand.

Or just ask Claude, ChatGPT or Cursor

Everything you see in the panel, your AI agent can do through the ArduMaker MCP server: with your authorization, within the scope you grant, and with every action audited. See what the MCP does

Frequently asked questions

Services that go well together

• Domains and SSL: A free subdomain or your own domain with Let's Encrypt, an nginx proxy with rollback, and port forwarding.
• Services and scheduled tasks: Create systemd services for your app and cron-style scheduled tasks with logs, without writing systemctl.
• Docker: Enable Docker in one click and manage images, containers, logs, volumes and networks from the panel.