Self-hosted quick start for technical evaluation
This page is for teams that want to run LaraDep internally or verify it technically before deciding on the managed option. The Docker distribution lets you start a full stack locally without cloud dependencies.
When to choose a self-hosted evaluation
- Compliance or internal policy requires running on your own infrastructure.
- You want to technically validate how LaraDep works before deploying to production.
- Operations will be managed by an internal platform or DevOps team.
- You need data ownership and full control over configuration and templates.
Recommended process
- Start the local stack — download the Docker distribution and start the stack using the application documentation.
- Base configuration — set up the first project, add a test server, and configure access rights.
- First test deployment — pick a template, fill in values, and run the deployment. Verify the flow: safety checks, deployment progress, and the recorded outcome.
- Evaluate fit — compare self-hosted operation with the managed option based on your compliance, team, and maintenance requirements.
Managed vs self-hosted — summary
The managed option suits fast start scenarios, lower platform overhead, and cases where running your own infrastructure does not add value. Self-hosted makes sense for compliance, internal data ownership, or when you want to manage templates directly in the database. Both options share an identical feature set.
If you are not sure which fits better, start with a managed demo — we can tailor it to your specific workflow.
Next step: Compare operating modes on the managed vs self-hosted page.