How to scale your data ecosystem with Vendia Share

Vendia Share simplifies the process of sharing data in real-time between organizations in a controlled, secure, and ledgered manner. Traditionally, sharing data in this manner is tough. There are several challenges that come to mind.

Challenges in multi-partner data sharing

Maintaining a single source of truth between organizations can be difficult. Databases are a popular information store, but securely sharing data from them with other organizations involves a number of compliance, security, and networking considerations that often mean slow action. Some organizations choose to share critical data with partners via spreadsheets. Using this method presents its own set of challenges. It's not apparent which spreadsheet is the latest and most complete source of truth.

[Vendia Share]( helps you solve this problem by provisioning a node for each organization that you wish to share data with. Each node provides a consistent view of the data that is shared with other parties, and each node has its own API endpoint dedicated to the organization that needs to securely access the data.

Centralized approaches to data sharing often result in disjointed authentication (AuthN) and authorization (AuthZ). The central organization will likely have a preference for how partners will log in to access data. It will also likely have existing tooling and mechanisms in place to support users. However, partners in the data network may have different means of authenticating and managing users. Vendia Share is flexible enough to allow each participant in a Uni to configure their own authorization type.

Onboarding new participants to a partner data network historically has been difficult. Often technical teams need to update topologies and networks for each new addition. The steps involved to bring in a new partner can take days if not months. Vendia Share reduces the time to minutes and does without the support of highly valuable engineers, as you will see in this post.

Getting started with partner onboarding

Creating Vendia Share accounts

Vendia customers share data using a Vendia Share Universal Application (or "Uni" for short). Each participant in a Uni has a dedicated node for reading and writing data. We will simulate two companies sharing data by using two Vendia Share accounts. If you are not familiar with how to create a Vendia Share account, please consult our Getting Started documentation. We will refer to these accounts as Account 1 and Account 2. You will create your Uni using Account 1. Account 2 will be invited to join the Uni and create its own Vendia Share node.

NOTE: The example in the blog will use two separate Vendia Share accounts associated with the same email account. I've used the plus ("+") sign to associate two Vendia Share users with the same email account.

Creating a Uni

For the purposes of this walkthrough, we will use the Product Catalog from our Quick Starts. Once you've created a Uni using Account 1, feel free to proceed with the remainder of the steps in this blog.

NOTE: The commands below assume a Uni name of test-uni-management. Adjust commands below that use the Uni name to match the one you used.

Inviting your partner(s0

Now that the Uni is up and running, you will invite Account 2 to the Uni. You can do this either with the Vendia Share web app or the Share CLI. For the purpose of this blog, you'll use the CLI syntax. My Account 1 e-mail address format is and my Account 2 e-mail address is

Vendia Share features RBAC support for controlling who has access to your Uni - we will be posting a more detailed blog of how that capability works in a future blog post. One of the RBAC features is the ability to invite another Vendia user to create a node and join your Uni. We accomplish this task with the following command.

First, ensure you have authenticated to the Share CLI using the share login command. Be sure to use the Vendia account associated with Account 1.

% share login
> Enter your Vendia email address
Enter your email:

> Enter your password for
Password: *********

✔  Logged in as

Once you have authenticated successfully, use the share uni invite command to begin the invitation process.

share uni invite --uni test-uni-management --user

NOTE: The name of my Uni is test-uni-management. Be sure to adjust the command and use the name of the Uni you created.

You will see output that is similar to the following:

Invite Successful

User successfully invited to Uni test-uni-management has been sent an email invite link.

For to join, they must:
 - click email link
 - OR join by running the share uni join CLI command with the token below

Invite token:    12345678-abcd-1234-abcd-123456789012
Expires on:      2022-01-30T02:26:24.872624

We will export that invite token as an environment variable (be sure to substitute your invite token in the syntax that follows)

# This command will save the Invite token for later use by **Account 2**
export VENDIA_TOKEN=12345678-abcd-1234-abcd-123456789012

Your Account 2 email address should have a message from Vendia, inviting you to join the Uni created by Account 1.

Joining the Uni with Account 2

You can use the Vendia Share web app when logged in as Account 2 to complete the Uni join process. You can click on the link included in the invitation email. However, I will show you how to use the Share CLI to complete the same task.

NOTE: Make sure you've created the VENDIA_TOKEN variable from the share uni invite output.

You will need to log out using share logout and log back in with share login. Specify the email address and password associated with Account 2.

% share logout
You are now logged out of

Run "share login" to log back in
% share login
> Enter your Vendia email address
Enter your email:

> Enter your password for
Password: *********

✔  Logged in as

Once you're authenticated as Account 2 you can run share uni join to accept the invitation and specify your node's settings.

share uni join --uni test-uni-management \
--token $VENDIA_TOKEN \
--config '{"name":"account2-node","userId":"", "region":"us-west-2", "settings": {"apiSettings": {"auth": {"authorizerType": "API_KEY"}}}}'

You will see output similar to the following:

addition of new node account2-node in uni addition of new node account2-node in uni is now in progress

NOTE: The name of my Uni is test-uni-management. Be sure to adjust the command and use the name of the Uni you created.

You can observe the deployment process of the Node for Account 2 by running the share get command.

share get --uni test-uni-management

You will see output similar to the following

Getting test-uni-management info...
│   Uni Information   │
Uni Name:
Uni Status:  ADDING
Node Count:  2
Nodes Info:
├─ ⬢ ProductCatalog
│  ├─ name: ProductCatalog
│  ├─ status: RUNNING
│  └─ resources:
└─ ⬢ account2-node
   ├─ name: account2-node
   ├─ status: DEPLOYING
   └─ resources:

To display schema & initial state, use the --json flag. Example: "share get --json"

The node creation process will take a few minutes. When the node creation is complete, feel free to step through the Product Catalog Quick Start and observe how data updates can be viewed by both participants in the Uni.


Once you are finished running the example you can delete the Uni. You will run the share uni delete command as Account 1.

share uni delete --uni test-uni-management

WARNING: Deleting a Uni is destructive and will remove all of its underlying data.

NOTE: The name of my Uni is test-uni-management. Be sure to adjust the command and use the name of the Uni you created.

You did it, so what's next?

Share your results on social media and tag Vendia (Twitter: @VendiaHQ, Linkedin: Vendia) so that we can see what you built!