A closer look at Navegante's features

By default, we use your repo's main branch as the production branch. If the automatic deploy is successful, we'll gracefully switch over your app to the new version. If it isn't, we'll keep your app running on the last known working deploy. If you'd rather run all deploys manually, you can disable automatic deployments in your project settings.

Preview URLs allow you to see changes from a designated preview branch before you merge them to main. Previews are meant to evaluate how application-layer changes (such as front-end and business logic) behave when deployed to the Internet. Currently, preview branches share the same environment variables and managed services as your production deployment. If you need a dedicated "staging environment" with its own database, we recommend creating a separate project for complete isolation.

All deployment actions are logged in Navegante. If you need to go back to a previous deployment, we provide a list of known working deployments you can rollback to. Once you've decided on a commit to roll back to, we run a deploy and only switch you to it if it works with no issues.

All projects deployed on Navegante come with a free navegante.app subdomain. If you have your own domain name, you can attach it to your app for free.

Our managed services are production-ready templates that we use for our own infrastructure. Instead of having to create your own scripts, we allow you to scaffold services (like PostgreSQL and Redis) and directly connect them to your application.

All managed services are automatically added to your project's environment variables. Managed services are also included in your project's observability stack, allowing you to identify bottlenecks in your services.

Managed services live on the same network as your app and don't have to travel to another server. We also don't expose your managed services to the public Internet. We rely on local networking to securely connect your web application (which is exposed to public Internet) and your services.

Each deployment you run on Navegante is logged. This helps you validate whether a deploy is running the tasks its supposed to run.

Cloud deployments sometimes behave differently from localhost. Real-time application logs can be valuable in critical moments where you need to ship out a fix.

Good application performance leads to good user experiences. Bad application performance leads to user frustration. Knowing how your app actually utilizes CPU, RAM, and Disk can help you improve the overall feel of your app and identify opportunities for optimization.