Introduction
Welcome to Ecosystem
Ecosystem is a low-code iPaaS (integration platform as a service): you design integration workflows and system connections through a visual interface, without re-coding everything by hand. It is aimed at technical teams and IT departments that want to speed up the setup and operation of data flows.
Context: why an integration platform?
Data integration has long relied on different technologies, each with its own limitations:
- EDI (electronic data interchange): automated exchanges via standard formats or value-added networks, used before the iPaaS era.
- ESB / ETL: enterprise service buses, designed to connect on-premise resources but unable to handle cloud integrations — which is what gave birth to the iPaaS.
- iPaaS: handles integrations in the cloud and between cloud and on-premise (hybrid integration platform).
Ecosystem is an EiPaaS (E = enterprise): it inherits the hybrid capability of the iPaaS and steers it toward enterprise use, aiming for zero-code with AI support (low-code approach).
Why use Ecosystem?
- Make SaaS or OnPremise solutions communicate
- Receive and process events point-to-point
- Import large volumes of data in batch
- Expose "simple" calculation APIs without storage
What you can do with Ecosystem
Orchestrate workflows
Define sequences of automated actions in response to events. Build complex workflows with an intuitive visual interface.
Connect systems
Integrate SaaS (Software as a Service) applications and existing ("legacy") systems in a few clicks, without writing an integration.
Simplify development
Compose preconfigured nodes (API, JavaScript code, FTP, loops, events, AI agent…) instead of developing and maintaining integration code.
Analyze and monitor
Review every execution of your workflows to debug, replay, optimize and follow your integrations in real time.
How to use this guide
This guide follows a goal-oriented logic:
| You want to… | Where to go |
|---|---|
| Understand the platform (concepts and vocabulary) | Concepts |
| Learn step by step (login, navigation, first workflows) | Getting started |
| Complete a specific task (create a trigger, deploy, filter traces) | the "Create…" / "Manage…" pages of each section: Triggers, Workflows, Traces… |
| Understand a concept (statuses, credentials vs dictionaries) | the Introduction pages of each section and the Best practices |
| Check a value or an option | the exhaustive lists: Trigger types, node catalog, Roles and permissions |
| Define a term | the Glossary |
The mental model in one sentence
A trigger starts a workflow, and each execution produces a trace. Environments isolate your deployments, dictionaries parameterize your values, authentication methods secure your access, and resources / Apps organize the business scope — see Concepts for details.
Next steps
- Concepts — concepts and vocabulary
- Getting started — login, navigation, first workflows
- Create a trigger
- Create a workflow
See also: Best practices · Roles and permissions · Glossary · Release notes