Guides / Index
Resilis setup guides
Choose a practical guide for the application and tools you already use. Follow a small Node.js example from source to a public response, or connect an AI agent before deploying local work. Each guide links to the product documentation so you can check prerequisites, supported operations and limits along the way.
Get started
Decide whether your source is on GitHub or in a local workspace. The dashboard route connects a GitHub repository. The workspace route uses an authenticated agent with local file and command access, plus Git. Review sensitive files before uploading source and select the intended organization before creating resources.
Deploy by stack
The task board examples offer three concrete ways to deploy a Node.js app. Start with Railpack when you want automatic build detection, choose a Dockerfile when the repository defines its own container build, or add PostgreSQL when records must persist. Use the included verification steps to check the running app rather than relying on a successful build alone.
- Node.js with Railpack — For Node.js developers, follow the task board from repository settings through a verified deployment.
- Dockerfile deployment — For developers who own a container build, deploy the same app with explicit Dockerfile configuration.
- GitHub deployment — For teams bringing an existing repository, authorize GitHub and select the source branch before deployment.
- Node.js with PostgreSQL — For developers building a data-backed app, connect a database and test persistence after redeployment.
- Apps and deployments — For app owners adapting an example, check source, runtime settings and deployment recovery behavior.
Deploy with an AI agent
Connect your client to the Resilis Model Context Protocol (MCP) server, then sign in and review requested access. The client-specific guides cover setup and tool discovery. Authentication is separate from permission to perform an operation, and the agent needs local tools for workspace deployment. Review each proposed change to a running service.
- Codex setup — For Codex users, add the hosted MCP server, authenticate and confirm that the connection works.
- Claude Code setup — For Claude Code users, configure the remote server and verify its tools after authentication.
- Agents and MCP — For developers checking permissions, read the shared authentication and workspace deployment requirements.
Data
Keep application deployment and database recovery separate when following a tutorial. An app rollback does not undo a schema change. Snapshot and point-in-time recovery availability depends on the plan, resource configuration and available restore points.
Billing
Check the expected resource usage before creating a long-running example. Plan fees become runtime credit, and build overage is separate. Review current resource floors and period allowances before estimating the total.