Self-hosted mode — running LaraDep on your own

Self-hosted mode

Self-hosted is the path for teams that want to keep running LaraDep fully in their own hands. The instance runs on your server, data stays with you and you have direct access to the structure, configuration and template management in the database. It is the choice for experienced teams with their own technical capacity and for organizations with internal security requirements.

What makes self-hosted different

• the instance runs on your infrastructure, data does not leave your environment,
• direct editing of Ansible configuration and custom modifications,
• full control over structure and configuration,
• room for advanced internal workflows and multi-tenant isolation.

Installation and start

• Installing a self-hosted instance — Docker, Laravel Sail, environment configuration and data initialization.
• Docker quick-start — quickly bring up an instance in a Docker environment.
• Preflight and self-hosted deployment readiness — validate access and rollback before production.
• First deployment and production checklist — prepare a server, run preflight and execute the first deployment.

Deployment and templates

• Guided deployment and preflight validation — how the runtime is exported and executed, with readiness checks.
• Templates and workflow — the composition model, assembling templates from modules and updating them in one place.

Security and team

• Workspaces, access and security — workspace isolation, roles, encrypted access and audit trail.

AI and automation

• AI assistant for your server — Claude, Cursor or Windsurf via MCP, without access to passwords.

Operations and governance

• Self-hosted day-to-day operations — repeatable operational process and change checklist.
• Runbook and governance — operations runbook, audit trail and compliance-ready standard.

Next steps

• Self-hosted onboarding checklist — practical pre-flight checklist before first production run.
• Preflight and self-hosted deployment readiness — use before every medium or high impact run.
• Self-hosted governance and change control — roles, scope and evidence standards.
• Self-hosted operations — operational rhythm and recurring run process.
• Self-hosted troubleshooting — restore operations when issues appear.
• How to switch to managed — what to check before changing operating mode.
• Self-hosted vs managed comparison — clarify trade-offs.

Is self-hosted right for you?

Self-hosted makes sense when data must stay on your infrastructure, you want to edit templates directly in the database, or you have your own technical know-how and want full control. If you would rather have a fast start without maintenance, see the managed mode or the comparison of both modes.

Next step: Continue to the Docker quick-start, or compare with the managed mode.