Focus on the game changers

not on enabler technology

When looking at modern IT architectures with microservices and new deployment models in public or private clouds, the software that is written and deployed must adapt to these requirements. But it's not an easy task to do this transformation and a new set of tools and services has to be implemented.

With elastic items as a platform for modern applications you can benefit from the work that was done to integrate and specialize existing base technology for usage in highly scalable applications. Every component is built with distributed applications in mind, and with a focus on manageability by non-technical staff for routine tasks.

The primary focus of developers should be on customization and tailoring of business-critical and unique functions where standard functions and operation of normal technology just consumes manpower. With the platform your team can deal with the hard problems and benefit from the specialist knowledge we have condensed into features like search & data management.

Frequently Asked Questions

Here are some details to some specific questions that we collected from our customers.

Usually the first thing we do after understanding the project goals is to create a demo or prototype with a test data set. This way we can start iterating use-cases in a very early stage and also learn how the project-specific data works and what it takes to satisfy all requirements.

One of the first decisions is how the overall architecture looks like. Some customers want to integrate on top of the APIs, others need a full-stack solution including frontend. We offer multiple integration scenarios and it is unlikely we don't find a way to communicate with the existing technology stack.

No, absolutely not. We have multiple scenarios where customer code is the entry point. We have a frontend solution but we can also satisfy microservice integrations and even support inclusion as a set of libraries to choose from. This depends entirely on the structure of the project.

No, probably not, not yet.

When loading data we have a flexible process framework that allows for a multitude of formats including common exchange file types like CSV or XML, along with direct database connections and custom APIs and custom code.

All primary data is available through the search and/or data API and can be managed through these. On top of that, processes and status information is available through APIs of the backoffice application that allows for integration in custom workflows.

We are offering RESTful APIs that return JSON data in most cases. This is usually very easy to integrate, it also supports our data-driven approach to APIs and data can still be validated through JSON Schema.

Hi, my name is Eliza. How may I help you?

We have connected multiple user-rights management systems to restrict searchable data. Users will always see a consistent view on their data while we only maintain one data source. In the data APIs, you can also offer read-only access to selected data and implement further security measures on top of the underlying role-based authorization model.

Yes, for integration with other systems we can offer simple token-based authentication as well as more sophisticated OAuth implementations. API users can be managed from the backoffice and also carry standard restrictions for multi-tenancy.

While it's still possible to physically separate tenants by running multiple, possibly containerized instances, for a resource-optimized solution supporting large numbers of tenants this needs to be carried through all layers of the application. We have already done this for you so you don't have to.

Our base frontend can be extended, overwritten or replaced with custom code through our overlay mechanism that allows us to offer a standard skin where you might only change a logo, override selected templates or use it as base for your entirely custom design.

Yes, as long as you are using standard JAVA code based on the Spring Framework and Spring MVC it will be very easy to run your custom code along with the platform and even using the core services in your own code, like implementing Configuration Management through the backoffice.

Depending on the deployment model and licensing you can push your customization code to the repository and do customization yourself or have your team work on the product.

No, but you can easily make it yellow by overriding style.css.

We offer flexible and adaptible licensing, ranging from pure SaaS licensing to full code licenses. Get in touch with us to have us work out what the best model for you might be.

Yes you can. By doing this or having this as part of the project scope you can do anything you like with the code. If you want you can still subscribe for core updates and bugfixes or use-case specific support.

In theory yes, we are working on a more vertical separation to support more usage-oriented licensing. You can ask us for the state of affairs on this undertaking if you think this might be beneficial for your use case.

Platform Components

Here is an overview of the tools and services that are available, complete with their respective backoffice management tool:

Site Search

A configurable search API with filters and aggregations that can deliver rich autocompletes as well as support hierarchies and respect user rights.


A flexible NoSQL Backend can store and process complex data structures and due to it's data driven nature is very easy to configure and scale.


With connections to messaging systems and internal event handlers your platform can tap into event-driven workflows and avoid batch processes.

Job Process Manager

With a integrated data processing infrastructure that allows managing batch processes and run data import & transformation tasks, processes that were hidden inside your tech stack become manageable by operative managers.


Our components allow for user-based security and authentication on several levels, from user registration and activation and API users to backoffice user management that allows multiple roles to be defined and selective access to backoffice tools.


When running microservices, orchestration, analytics and reporting becomes one of the keys to understanding problems and bottlenecks in your infrastructure. All components have analytical APIs and come with a integrated analytics solution.