Docs / Index
Documentation
Find the Resilis documentation for your next deployment. Start with the product basics, choose a build workflow, then check the data and billing requirements for your app. These pages describe supported operations and their limits so you can choose a suitable starting point before changing a running service.
Get started
Resilis provides app hosting, managed databases and object storage. You can use the dashboard for a GitHub repository or connect an AI agent that can work with local files. The two routes have different prerequisites: the workspace route needs local Git and command access, while the dashboard route needs an authorized GitHub connection.
Deploy by stack
Choose an example that matches how you build your application. The task board guides use a small Node.js app to show deployment and verification. Railpack detects supported project settings; a Dockerfile gives you an explicit container build. Check build logs, runtime settings and the public response before treating a deployment as ready.
- Apps and deployments — For app owners, understand source settings, build configuration, deployment status and recovery limits.
- Node.js with Railpack — For Node.js developers, deploy the task board using automatic build detection.
- Dockerfile deployment — For developers maintaining a container build, deploy the task board from its Dockerfile.
- GitHub deployment — For teams with existing repositories, connect a repository and review the branch and app settings.
- Node.js with PostgreSQL — For developers adding persistent data, bind a database and verify that records survive redeployment.
Deploy with an AI agent
The Model Context Protocol (MCP) connects an agent to supported Resilis tools. Sign in and review the requested access before granting it. Your agent writes the app; Resilis supplies cloud operations within the permissions you authorize. Connecting a client does not grant unrestricted production access.
- Agents and MCP — For developers choosing an agent workflow, understand authentication, permissions and local workspace requirements.
- Codex setup — For Codex users, add the Resilis server and complete the authentication checks.
- Claude Code setup — For Claude Code users, connect the server and verify available tools after signing in.
Data
Database and application recovery are separate operations. Rolling back an app does not reverse database migrations or restore its data. Plan and target checks apply to managed resources, and recovery depends on the configured protection and available restore points.
Billing
Review resource usage before sizing an application. Plan fees become runtime credit, while build overage is billed separately. Resource floors and activation boundaries affect estimates; existing billing periods can retain recorded allowances.