Also use TerminusCMS data products in DFRNT

Use TerminusCMS data products in DFRNT

Additionally to DFRNT hosted data products, you can connect and collaborate directly on data products hosted at TerminusCMS from DFRNT, using TerminusDB API keys. helps you manage data products that are either hosted in DFRNT through the subscription, or connected via API. Data products hosted at TerminusCMS can be reached by adding an API key found in your TerminusCMS profile at .

To get started, the first step is to connect your data product instance at TerminusDB, here's how:

  1. get an account, and setup a data product at TerminusDB/TerminusCMS
  2. connect the data product to

Step 1: Create your data product in TerminusCMS/TerminusDB

A suggestion is to bring up a text editor to save the values you need for later.

  1. Join the TerminusCMS offering at TerminusCMS
  2. Sign up for an account (Remember that the team name will be used later)
  3. Confirm your email address
  4. Login to to create your data product
  5. Create the data product (note that the id and name are not the same), you will need the data product id to connect to
  6. Create an API key for connecting to TerminusDB (upper right/profile in the menu)
  7. Add a token description, generate new token and copy it

You should now have the three things you need to connect Zebra to your data product:

  • A TerminusDB Team name (See your Profile to find it)
  • A Data Product ID (See about the Data Product)
  • The API key (Create one in the profile, you can create as many as you need)

Step 2: Connect to TerminusDB

  1. Sign up for through the sign-up on the homepage
  2. Once logged in to, go to Settings/API Keys. Or use the guided setup at Learn More/Start Free.
  3. Add your Settings/API Key: Fill in the TerminusDB Team (that your captured above), “Token” and the API Token (see above)
  4. Complete filling in the details for your team/instance; the setup is similar for the localhost subscription
  5. Team/Instance: Fill in TerminusDB Team (connects using the server-side vaulted API token) as both team name and team reference
  6. Team/Instance: Set the id to commit as, you likely want to use your email address (like you would if you use git)
  7. Create a named TerminusDB connection pointer to a data product branch in your team/instance, or create a sandbox data product. In settings, this is part of the team-specific settings.
  8. Pointer creation: Select your TerminusDB Team
  9. Pointer creation: Enter your TerminusDB data product id (see above)
  10. Pointer creation: Set the branch you want to be working on (usually main)

If all went well, you should now be ready to add your schema and data in the Model Editor.

If you encounter any errors, feel free to submit an issue at Github/issues. Be careful to check that you share no secret information, like the API token if you copy/paste a screenshot.

    • Related Articles

    • Overview of DFRNT data modelling

      The data model in DFRNT data products follows the TerminusDB graph metamodel 1:1, and enables easy data modelling and advanced visualisation The data modelling capabilities of involves five categories of data structures: Records, ...
    • How can I learn more about DFRNT

      Learning about DFRNT is closely connected to leveraging the open source TerminusDB data product engine, for which DFRNT is a UI and hosting provider. DFRNT is a user interface and hosting provider for the open source TerminusDB data product ...
    • The DFRNT Data Product Builder

      DFRNT is a data product builder with knowledge graph visualisation, modelling and management, with version control, API access and a datalog engine. With DFRNT data products, digital architects, cybersecurity professionals, data practitioners and ...
    • How to get started with the Logical Studio?

      With the Logical Studio, you setup a branch in your data product for saved and reusable logic blocks. When you start the Logical Studio for the first time, it presents you a guide for setting up a new branch (data workspace) with a specific logic ...
    • Data product translations as branches

      The recommended way to maintain data product translations is to use the branching method, where each branch corresponds to a language, and use a common schema where each label is translated as part of the schema documentation. Data product ...