You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
• Can Vaulty (or a fork) be configured, modified, or extended to work from a client/end-point? For example, it (or an extension) installs to a browser and automatically tokenizes data entered into form fields on the cloud. That way, a user could use it with multiple cloud-based applications without depending on third-party developers installing Vaulty to the cloud-application backend(s).
• Can it be set up to store data on a local hard drive or SSD instead of a redis server?
• Do you still have plans to make Vaulty production-ready, and if so, is there a tentative timeline?
The text was updated successfully, but these errors were encountered:
• Can Vaulty (or a fork) be configured, modified, or extended to work from a client/end-point? For example, it (or an extension) installs to a browser and automatically tokenizes data entered into form fields on the cloud. That way, a user could use it with multiple cloud-based applications without depending on third-party developers installing Vaulty to the cloud-application backend(s).
• Can it be set up to store data on a local hard drive or SSD instead of a redis server?
• Do you still have plans to make Vaulty production-ready, and if so, is there a tentative timeline?
The text was updated successfully, but these errors were encountered: