We are constantly developing Exolink and adding new features or components to further improve our service. On this page you will find an overview of the latest updates - a regular look at this page is worth it. You are missing a feature? Let us know and use our feature board to share with us directly:
Working with multiple instances in Exolink? New to the Exolink Manager menu is the Instance List item, which takes you to an overview of all your instances. Here you can edit your instances, temporarily suspend or permanently delete them, change permissions or update instances when there is a new version.
To make logging in to Exolink even easier and more secure, we now support the FIDO2 standard for authentication. To activate FIDO2 in Exolink, you need to activate a security key for e.g. your mobile device, a U2F token, etc. once in your Exolink profile and you are ready to go.
Do you want to write your own code in your preferred language for your Exolink Flow? With our new Functions components, you can easily run your AWS Lambda and Azure functions and re-use the result. This allows you to develop code for basically any type of application and seamlessly integrate it with Exolink without deploying or managing servers.
Below the navigation item "Log", you will find the new Exolink Log, which logs logins and changes to plans, instances or users. The log entries are kept for 6 weeks and can be read out via the search field and the date selection. The currently displayed log can be saved as a CSV file via the "Download log" button. The authorization to view the log can be assigned per plan and instance under the corresponding navigation items.
From now on, connection data that is available in all instances of the plan can be stored per plan in the Exolink Manager. For this purpose, only the connection type has to be selected and then the corresponding information has to be entered. At the beginning this is possible for MySQL connections. This means that the data only has to be entered once by a plan owner or plan admin and can be used directly within the instances in the corresponding component, but cannot be viewed.
Suggestions, improvements or even praise - we would love to hear from you. Feel free to write us at: