Skip to content

Taipy's Core configuration

In the previous chapter, the main Taipy Core concepts are defined.

Taipy Core is an application builder designed to help Python developers efficiently turn their algorithms into an interactive production-ready data-driven application.

To build such an application, the first step consists in configuring the characteristics and the desired behavior of your application and its entities.

Reminder: Config vs Entities

Throughout the documentation, configuration objects are named configs (DataNodeConfig, TaskConfig, and ScenarioConfig), while runtime objects (DataNode, Task, Sequence, and Scenario) are called entities.

One thing to wrap your head around (it may not be very intuitive for everyone at first) is that the configs are really just configuration objects specifying the characteristics and behaviors of the runtime concepts they relate to. Configs can be seen as generators. Indeed, each entity is instantiated from a config. Note also that the same config can be used to instantiate multiple entities.

More details on the entities are available in the Entities chapter.


All configuration objects must be created before instantiating any entity or running the Core service.

Any modification to the configuration objects after the Core service has been started or an entity has been instantiated will raise an error.

This chapter is dedicated to the configuration and focuses on the various configs objects. Its sections are organized as follows:

The next section introduces the Config singleton.