Stashr provides comprehensive coverage for Salesforce Marketing Cloud, including:

Content Builder and Shared Content

Data Extension and Shared Data Extension configurations

Automation Studio: Specifically, automations and their related dependencies

Web Studio: Cloudpages and Code Resource Pages

Automation Studio and Data Extension Monitoring

We love this question! Here’s what’s in store:

Journey Builder Support: This feature is high on our priority list. We're actively strategizing on how to extract valuable insights from Journey Builder and determining the optimal approach for integration.

Triggered Send Monitoring/Activation/Backup/Recovery

Data Extension Monitoring Rules and Notifications

ETL Process management for Data Extension Data transfers to your file locations

Full Automation Recovery and one-click re-Activation

At Stashr, we prioritize security above all. Take server-side JavaScript script activity as an instance. When interacting with the Marketing Cloud REST APIs, you require API credentials. To prevent these keys from being version-controlled, Stashr implements advanced security measures. Users can designate the keys they wish to redact. Upon commit, Stashr substitutes that value with a placeholder key. During recovery, Stashr reverses this process, seamlessly restoring the original key value, eliminating the need for manual intervention.

You can recover assets from the moment you create the instance or install Stashr. This highlights the significance of installing Stashr early, ensuring comprehensive asset protection from the get-go.

Currently, there's no time limitation on accessing commits. As long as you've created a snapshot, our aim is to keep it accessible indefinitely.