What stage of development is Kendraio App currently in?

It’s very early days for Kendraio App. The app currently only exists as a demo in an early alpha version. However, we constantly build new features and workflows and integrate with new APIs as part of our pilot projects (like the one we did with Teosto).

Because we are a non-profit organisation, we do not have the capabilities of creating a commercial product. As such, the design of the Kendraio App is pragmatic, and ideally, it should serve as a way to kickstart your imagination and to show all that it could be one day.

Who is Kendraio App for?

Currently, we are focusing on the creative industries with a focus on the music industry. Kendraio App is for anyone in the music industry who has a lot of admin work to do that involves different services. It can help artists and their managers keep all their data in one place, collaborating more easily and even arranging payment splits. It could help CMOs and publishers to keep track of royalty payments and contracts. It can be used to keep track of and compare social media engagement and streaming statistics, visualising and analysing data more easily. Do you have a use case? Get in touch!

But our use cases don’t end with the music industry. The possibilities are endless: if there’s an API, we can connect to it.

Does Kendraio App require a specific data structure?

Kendraio app meets the person or data provider where they are. So no, we work with their native formats. Eventually, we want to be able to work with all data structures, so tell us if you have one.

Can you create a workflow between two different services?


How long would it take to build a flow for a new service?

Right now, as we’re in alpha, it takes our developers around half a day or a couple of hours, once the initial problem has been outlined. Our goal is for Kendraio App to be a user-friendly plug-and-play app for professionals.

What makes Kendraio App different from other workflow builders, dashboard apps or services?

Many of them are services, whereas Kendraio App is an app. This means that Kendraio has no way to access your data, and all your interactions are directly with the service you’re using via their API. Read more about privacy and data in the next question.

In Kendraio App, the user also has more control over the look, feel, and flow of the app. We want you to be able to pick anything from colours and fonts, to site layout and data format.

How does Kendraio App handle privacy and confidential data?

Kendraio App is not a service, it’s an app that is locally run - this means that any interactions you have with APIs integrated with Kendraio App remain between you and the service. Kendraio, the organisation, can’t see any of the data going from user to service provider, it only helps you pull it from there and display and work with it.

In comparison, when you’re looking at a website through a browser, much information flows both ways. This creates many vulnerabilities and it is what we want to avoid at all costs. The basic structure of an APIs are more restricted and you know what’s being sent both ways.

How can I help/contribute to Kendraio?

Kendraio is a non-profit initiative and so is always looking for both paid and volunteer contributors. You can have a look at our code on our Github and provide us with feedback. If you want to stay up to date follow us on Facebook, LinkedIn or Twitter, or join our public Slack.