Deploying Tranquil Data in 4 Easy Steps
Now that you’ve read about what Tranquil Data does for you, let’s get you running. It only takes 4 steps. Each of them is designed to be super-simple for a specific role. Read to the end to learn about how we can help you move even faster with our formal pilot program.
Step 1: Deploy the Software
The Tranquil Data™ Trusted Flow Edition is provided as a docker container. In its simplest form it only requires a durable volume, so it can be deployed by anyone who has basic knowledge of how to use Docker Desktop (locally) or some framework like Kubernetes or ECS (in the cloud). Typically this is someone in IT, Operations, or Engineering.
To test out the software locally, once you have our image, you run:
docker run tranquildata/trusted-flow:latest -p 8890:8890 -e TRANQUIL_CONTEXT_STORE=localNow you can point your web browser at localhost:8890 and get started with step 2. For production you would mount a durable volume, configure security settings, and capture logs and trace to known endpoints, and as we describe later we’ll help you get through that quickly, but the above command is literally all it takes to try out Tranquil Data.
Step 2: Configure the Software
Once you have the software running, it’s time to configure the rules that constitute correct use. While there are APIs to automate this process as you scale, to get started there’s a simple UI for legal and/or privacy roles. In most organizations you’ll start with one existing, documented set of requirements like a privacy policy, a back-end contract, consent for a clinical trail, or age-restrictions on data use. It should take about 15 minutes to use the first of these to learn how Tranquil Data works.
Once you’re done you can start adding requirements incrementally, and a single dashboard view shows that you’re getting what you expect. In short-order you’ve taken documents that today need to be interpreted manually and created a source of truth that automates enforcement going forward.
Step 3: Connect 3 API Calls
The first way that most organizations actually put Tranquil Data to use is as part of the user onboarding process. This is done by a software engineer, in a web or app team, that implements the User Experience of creating and logging into an account. There are exactly 3 REST APIs to call:
- Before a user creates an account, an API call to get the personalized terms that apply to that user based on the above configuration.
- After the user has agreed to these terms, and made any additional, discretionary consents, an API call to record the consent
- Whenever the user logs logs in later, an API call to see if the configuration has changed such that the user must re-consent
That’s it, and for most applications this is a pretty standard and simple CX flow. By implementing just these three touch-points, legal & privacy teams are now certain both that users are agreeing to the right terms and that developers are correctly implementing processes required by regulations and contracts.
Step 4: Support Self-Service Data Use
At this point, Tranquil Data is delivering tangible value. There’s usually a lot of time spent between legal, privacy, product, and engineering discussing what it takes to implement these onboarding and re-consent processes, not to mention re-visiting each implementation to see if they’re still meeting requirements. If all you do with our product is automate-away this one pain-point, and you’re a large organization, you’ve probably just saved hundreds of thousands of dollars in FTE time and duplicated resources.
But we’re not stopping there. While there are additional points of API and Database integrations that you can now connect, there’s also a self-service component of the product that you’ve actually already configured for use. With no additional work, the product exposes a UI that lets anyone in your organization upload a CSV and get back the valid (redacted) subset for any given purpose.
An audit trail in the background captures the details. Now (e.g.) a marketing team can filter down all customers to the valid set for a given campaign, or an account team can determine which sets of data to share with a B2B customer, all without asking for help. Those sales & marketing teams get to move much faster, while legal & privacy get the time back they would have spent researching and answering these questions to help their companies grow.
An aside to the technical readers: if you want to implement this filtering feature for your business teams, but don’t have Tranquil Data “live” in your applications (from Step 3) yet, there are API calls so you can asynchronously create user context to get started.
We’re Here To Help
In practice, we’ve found that most companies need some form of the flow above. If that’s you, join our Early Access program! We’ll get you signed up and started with the product, documentation, and common examples. We also have a simple pilot program where we’ll help you get through everything we talked about here in half a day. This is a great, easy way to get familiar with Tranquil Data and see the immediate value first-hand.
This simple path is where most people start. If you’d like to go a little deeper, however, and explore some of the additional integration-points we offer around decision tracing, context history, databases, and security frameworks, we have a second pilot program for you. It offers more interaction time with our team, and gives you the ability to define rule-sets that aren’t supported OOTB. In this Early Access phase of “Dragons” we’re working directly with anyone customizing use, so this is a great chance for you to get your requirements into our roadmap and get help shaping your future data platforms.
Either way, or even if you’re interested in learning about other flows we support, get in touch! We’ll get you started and feeling tranquil about your data in no time.
