Plans that grow with
your integrations

Yes, you can test the elastic.io iPaaS for two weeks. Please choose one of the plans listed above to sign up for the free 2-week trial. No credit card information required.

You can find the list of all available components specifically built to run on the elastic.io platform at Connectors.

The pricing strategy of elastic.io is a mix of transparency and readiness to negotiate based on the needs of each individual business. With elastic.io, you’re getting more integration credits than with other iPaaS providers, on any package plan. elastic.io also offers a 14-day free trial, with a pre-trial demo upon request.

An active step is a connector of a launched integration flow. Each connector represents a container that is used to execute a specific action, such as transforming data, making an API call, or routing information between systems. In simple terms, an active step is each individual connector of your integration flow while it is working. Active steps are used to measure platform usage and help control resource consumption across your subscription.

Messages are the units used to measure data processing within elastic.io integration flows.

Each time a flow step processes a record or event, it generates a message that is counted toward your subscription usage.

Messages are tracked across all executions of your integrations and are used for monitoring and billing purposes.

They help define how much data your flows process within a given period, typically within a monthly quota.

In simple terms, messages represent the number of individual data items your integrations process.

Contracts and Workspaces are part of elastic.io’s platform structure that helps you organize your integrations and teams.

A Contract is your main environment on the platform — it defines your subscription scope and includes users, permissions, and one or more Workspaces.

Within a Contract, Workspaces act like folders where you build and run your integration flows, manage credentials, and collaborate with specific team members.

Each Workspace is isolated, so you can safely separate development, testing, and production setups.

In short, a Contract is your overall account environment, while Workspaces help you organize and operate your integrations inside it.

For more information, please refer to the article on documentation.

Yes — you can use elastic.io IPaaS without a technical background or programming skills.

The platform is designed as a low-code / no-code solution with an intuitive, browser-based interface that allows you to build integrations visually instead of writing code.

It provides a graphical integration designer, ready-to-use connectors, and simple data mapping tools that guide you through the process step by step.

This makes it accessible not only for developers, but also for business users who want to automate workflows and connect systems on their own.

At the same time, more advanced features are available if deeper customization is needed.

Yes, there are two ways to create a new integration connector. It can be done by your technical team, please follow the documentation page for detailed instructions. Alternatively, our Professional Services team can develop a custom connector per your requirements as part of a paid project.

If you reach the limits of your subscription, certain platform resources will be restricted depending on the type of limit exceeded.

For message (credit/task) limits, all flows in the contract will be suspended until the next billing cycle or until additional capacity is added to your plan.

If you reach the limit for active steps, you may not be able to run additional integration components until existing usage is reduced or the limit is increased.

In case of webhook request limits, incoming requests may be throttled or temporarily rejected once the quota is exceeded.

In all cases, you will be notified so you can adjust usage or upgrade your subscription to ensure uninterrupted operation.

Yes, elastic.io offers pricing benefits when you choose an annual payment in advance compared to monthly billing.

With an annual plan, the overall cost is lower than paying month by month, making it a more cost-efficient option for long-term use.

This allows customers to reduce their total spending while keeping full access to the same platform features.

An integration flow is a sequence of connected steps that move and transform data between different applications or systems.

Each flow defines how data is received, processed, and delivered using a series of components arranged in a specific order.

It can include triggers, data mapping, transformations, and delivery actions depending on the use case.

Integration flows run automatically once activated, enabling continuous data exchange between systems.

In simple terms, an integration flow is the automated workflow that connects your applications and moves data between them.

For more information, please refer to the article on documentation.

The Recipes feature allows users to leverage integration Flow templates for easy sharing and reusability. To accommodate scenarios where end users prefer not to directly manage the elastic.io platform, we offer the Embedded Recipes feature. It enables you to provide a direct link to a Recipe page for end users. This allows them to authenticate and activate Recipes without navigating the entire platform.

For more information, please refer to the article on embedded Recipes.

Yes, we offer an onboarding starting from the Enterprise plan. Training can be provided upon request as a paid service by our integration professionals.

White-label subscription on elastic.io is set up as part of an enterprise agreement with the platform provider.

First, you need to contact the elastic.io sales team to enable the white-label option for your contract.

Once activated, the platform is configured with your own branding, including logo, colours, and domain settings.

After that, your workspace and user access are set up under the white-labeled environment, so your customers interact with the platform under your brand.

The elastic.io team typically supports the initial configuration to ensure everything is properly aligned before going live.