Pricing

Frontstage is a headless application framework that allows to build high performant and platform-independent client applications. An application may consist of a single (static) dataset or may receive datasets dynamically (leading to different dataset variations), and an application may save user inputs in form of "user input objects"

A license is valid for one application and one platform. Price per license basically depends on how many dataset variations may arise and how many user input objects shall be saved.

Innovator

€ 350 / month

You need an easy to set up catalog with tonnes of products? Go for the basic version with no limitations for b2c.

Function Overview
  • Cockpit
  • Applications included: 1
  • Persisted user input objects: 100
  • Max entries per model: 10000
  • Catalogue Variations: 100
Buy additional options
  • 350 € per 1 Additional Platform
  • 350 € per 100 Additional Persisted User Input Object
  • 350 € per 1 Additional Application
  • 350 € per 10000 Additional Entries Per Model
  • 350 € per 100 Additional Catalogue Variation(s)

Professional

€ 1750 / month

Sophisticated performance with multiple custom catalogs for different users. Make a unique impression in the b2b market.

Function Overview
  • Cockpit
  • Platforms included: 1
  • Applications included: 1
  • Max entries per model: 100000
  • Persisted user input objects: 1000
  • Catalogue Variations: 1000
Buy additional options
  • 1750 € per 1 Additional Application
  • 1750 € per 1 Additional Platform
  • 1750 € per 100000 Additional Entries Per Model
  • 1750 € per 1000 Additional User Input Objects
  • 1750 € per 1000 Additional Catalogue Variation(s)

Enterprise

Nothing fits? Please contact us!

Don’t worry! Let’s catch up to find a tailored solution for your specific needs.

Function Overview
  • Cockpit
  • On Premise
  • Developer Support
  • Catalogue Variations: individual
  • Platforms included: up to 3
  • Applications included: individual
  • Persisted user input objects: individual
  • Max entries per model: unlimited

Do you have a special request? Please contact us.

What does "headless application framework" mean?

"Headless" means that the framework provides data and functions to access that data independently from languages, frameworks, or platforms used for building the user interface.
When building applications with frontstage, you can ...

  • use any language for building the user interface like html/javascript,objective-c,swift, or java
  • use other client-side frameworks such as angular, vuejs, or react
  • support various platforms for building applications, i.e. iOS Apps, Android Apps, (single page) web applications, or desktop applications.

Frontstage application framework offers lots of functions commonly used when building applications, like sorting, filtering, aggregating, building carts, and many more. Data and functions are provided on client-side in the format of the respective target language and platform.

Can I run the same application on different platforms?

Yes, you can. In terms of frontstage, an application is "headless" and can provide the same data model and functions to varios languages and platforms. If you like, you can take advantage of platform specific languages/frameworks like swift for native iOS Apps or java for native Android Apps. But you may also decide to build a platform-independent user interface in html5/javascript with angular, react, ...
Note, however, that multi-platform apps require additional licenses.

What is a data set variation?

An application's schema file contains references to a data set. These referene can be static, such that the application will load exactly the same data set. In this case, there are no variations. However, if references to data sets contain place holders, then the effective data set loaded depends on the value the respective place holder takes on. The possible values of a place holder define the number of dataset variations. If the schema file uses several place holders, then the effective combinations of these place holder values count.

Consider, for example, the following static schema. The patterns part does not contain any placeholder, such that the application will request (and consequently show) exactly the same data set.

Example: Static schema

@patterns:
application_model.json;http://myserver.content/papplication_model.json
products_data.json;http://myserver.content/products_data.json

The following dynamic schema, in contrast, contains a place holder {country} (denoted by the curly braces) in the patterns. The aim might be that different countries shall present a different range of products. With the place holder in ‘{country}/products_data.json’, the application may load a different ‘products_data.json’ depending on the value of {country}. The number of distinct values for place holder {country} thereby defines the number of data set variations available in the application.

Example: Dynamic schema

@patterns:
application_model.json;http://myserver.content/papplication_model.json 
{country}/products_data.json;http://myserver.content/{country}/products_data.json

What is a user input object?

A frontstage application may store user input for later retrieval or for processing through other applications. User input may be, for example, entered text or entries added to a shopping cart. Such user input is packed to an object and stored using an individual key, with which this user input object can be retrieved later. The maximum number of distinct keys for user input objects is relevant when configuring the frontstage license.