cenit

:rocket: Cenit IO - 100% open source integration Platform (iPaaS)

cenit-io
461
129
Ruby

cenit_io

Code Climate
codebeat
license

OpenAPIs in collection
OpenAPI specs
Endpoints

Follow on Twitter

Cenit

Is a 100% open integration-platform-as-a-service (iPaaS) that’s modern, powerful, yet hackable to the core, ready to use in the cloud or on-premises. It is designed to solve unique integrations needs, orchestrate data flows that may involve types of protocols and data formats, and provide API management capabilities. All of which can support a wide range of integration use cases. It is particularly valuable to embrace a pervasive integration approach.

To install and learn more about the platform check the documentation

Integration Platforms build on top of Cenit

Why

The insatiable need for integration driven by social networks, open APIs, mobile apps, cloud services, and increasingly, the IoT is fertile ground for the growth of integration platform adoption.

Many are familiar with services such as Zapier and IFTTT, which addresses common integration problems but have limited capabilities to adapt to particular needs and to reflect business flows that are not simple. iPaaS platforms are designed to handle this issue, being in recent years in the state of the art for applications and data integration technologies used by large organizations, and gaining increasing interest from the general public.

The proliferation and growing importance of decentralized integration tasks driven by business and IT trends are forcing us to rethink organizational models and technology platforms to an approach to pervasive integration.

None of the vendor leaders in the market offers a completely open and transparent solution, with the freedom to use, customize, or modified without restriction. We believe that is one of the keys to wide adoption, and it is relevant in deciding to use on-premise.

Value

Cenit makes it possible that the benefits of a modern iPaaS can be accessible to the small and midsize organizations, It is particularly valuable to embrace as a strategic component of a pervasive integration approach that allows complete automation of all operational processes. As well as adding value quickly and continuously, essential to be competitive in the actual economy.

How

  • Developing a 100% open source integration Platform (iPaaS).
  • Providing options to use in the cloud or on-premise server.
  • Including open catalogs for formal API specs.
  • Giving options to share integrations at different openness levels: inside a tenant, to specific tenants, or for everyone.
  • Ensuring that anyone can create, use and share integrations.
  • Being ready for enterprise environments.

Capabilities

  • Backendless: After creating a new Data Type using a JSON Schema, a complete REST API and a CRUD UI to manage the data are generated on the fly. Useful for mobile backend and API services.

  • Routing and orchestration: Integration flow development, monitoring, and lifecycle management tools. Enables multi-step integration flows by composing atomic functionality (such as connection, transformation, data event, schedule, webhook).

  • Data integration: Data validation, transformation, mapping, and data quality. Exchange support for multiple formats (JSON, XML, ASN), standards (EDIFACT, X12, UBL) and protocol connectors (HTTP(S), FTP, SFTP, SCP).

  • Third-party service integrations: Directory of Shared Collections to connect services as ERP / Fulfilment / Marketing / Communication.

Data Pipelines between APIs

It allows the creation of custom data pipelines to process, store and move data between APIs. The flows could be trigger by data events or be scheduled.

There are now over 200 pre-built integration collections shared out of the box to connect with online internet services,
fulfillment solutions, accounting, communications, ERP, multi-channel, etc.

see this video for more details

An example of integration data flow (Fancy <=> Shipstation):

  • Every 20 minutes Cenit triggers a flow to get orders from Fancy Marketplace.

  • New or updated orders are received and persisted in Cenit.

  • After the new or updated orders are saved, a Flow is triggered to send a shipment to Shipstation.

  • The flow requires transforming the Fancy Order into a valid shipment on Shipstation.

  • Every 20 minutes Cenit triggers a flow to fetch Shipped shipments from Shipstation.

  • After the shipments are updated in Cenit, a Flow is triggered to send the tracking update to Fancy.

Stack

  • Ruby
  • MongoDB
  • RabbitMQ
  • Redis

Contributing

Cenit IO is an open-source project and we encourage contributions.

In the spirit of free software, everyone is encouraged to help
improve this project.

Here are some ways you can contribute:

To the Community

Since the challenge is great, we have to build the solution in the community. We believe that a successful open source project provides confidence, facilitates creating a broad community, where everyone can share answers to questions, suggestions, and improvements to the platform.

We encourage the community to join the initiative and contribute to the dissemination of the project, sharing integration experiences, collaborating in the detection and resolution of errors, or contributing to the development of the project. We hope that those who join us enjoy the collaborative work and the challenge of achieving something innovative and useful that can potentially serve many others.

Screenshots

menu

tenants

cenit_type

mobile_view