Test and debug your code in your Sandbox environment
Play around! This is your development and testing playground. On your sandbox you can debug your flow and stabilize it.
Deploy your stable release to a separate environment when you're happy with it
Scale out with ease! Create highly available environments with a click of a button. Navigate to the Run section on your sidebar to create, update and delete existing environments.
Easily access your node documentation and usage information
Read more about your node of choice, its documentation is accessible directly from the canvas. Just press the Info tab located on the canvas bottom bar.
Use the debug node to print to the canvas debug tab, console or both
See your flows output by accessing the debug tab located on the bottom bar of the canvas. You are also able to see your container's log by navigating to the console tab right next to it.
Some canvas changes require a full deploy
Changes on canvas that will cause creation or deletion of endpoints will trigger a full deploy on your next run request. Node changes that are expected to cause a full deploy will appear as highlighted on your canvas.
Run your environment on distributed geo-located regions
Decide whether to run on a multiple or a single region mode. Control the number of running instances per each environment. Choose the best configuration for your app.
Access Logs, KPIs and usage metrics from the environment dashboard
Click on your environment to access important information such as logs, KPIs and metrics. From here you can also view important data such as your container's uptime and status.
Easily communicate with your application via the endpoint of your choice. HTTP, TCP, UDP, Websockets - Everything goes!
After a successful deploy, you will be able to find your endpoints information in your environment dashboard.
Perform advanced actions on your environment
From your environments dashboard you can stop/start your environment or a single region instance. From there you can also control the number of running instances and update the running release of your choice.
Luther basic update