Skip to main content

Open-source deployment

Deploy this folder. Or teach your agent.

Two doors. Tonight this folder becomes a URL, or teach Cursor / OpenCode on this machine.

project / app

Deploy

This folder becomes a URL.

No git required. One command in this directory, and Appaloft returns a live URL for this app on infrastructure you control.

  • No git required. Run appaloft deploy . in this directory.
  • Success is a live URL for this app. Failure must exit non-zero.
  • If you are not signed in, you will be asked. You also need a usable Server.
Deploy
project / appArchitecture

Agent

Teach the agent you already use.

appaloft setup agent writes skill and MCP into Cursor or OpenCode on this machine. It does not deploy.

  • appaloft setup agent writes skill and MCP into Cursor or OpenCode on this machine.
  • It does not deploy. Setup writes local files, not a live URL.
  • Codex still needs appaloft auth mcp login and appaloft auth mcp codex install.
Agent
project / appLogs

What you get, and how you check it.

A live URL you can open, skill files on this machine, and recorded facts. Not a badge.

Folder becomes a URL

appaloft deploy . in this directory. Git is optional. The outcome is this app's live URL.

Agent stays on this machine

appaloft setup agent writes skill and MCP into the editor you already use. It does not deploy.

Evidence is observed facts

Appaloft records digest, runtime, routing, health, and access. It does not claim formal correctness, security, or compliance for the application itself.

Compare and blog stay

Compare is how you pick a platform after you pick a door. Blog is engineering writing. Neither is a homepage catalog.

It runs on a server you control.

Appaloft is a self-hosted PaaS path, not a hosted Railway cloud. You need a usable Server. Success is still this app's live URL.

Your Server

Bring a machine Appaloft can use. The app does not run on a hosted fleet you do not control.

This folder

Git is optional. appaloft deploy . uses this directory as the app.

Live URL

A public route is attached after healthcheck. The outcome is this app's URL.

Need more than a folder?

Add the database and the rest of the stack.

Official Blueprints cover databases, storage, automation, AI runtimes, observability, and complete self-hosted applications. Each recipe carries the resources, ports, health checks, and bindings needed to run it.

Add the database and the rest of the stack.

Your app

The folder you want live

Blueprint

Postgres · storage health · secrets

  • Database
  • Storage
  • Health check
  • Port
  • Secret

Installed application

Resources · bindings deployments · evidence

Resource Binding

Pick one door.

Deploy the folder, or teach your agent.