Lobster_data Pricing Overview
Lobster_data pricing & plans
Top Rated Lobster_data Alternatives
Lobster_data Alternatives Pricing
The following is a quick overview of editions offered by other API Management Tools
 Free Edition | Free | Get started with a free integration flow at celigo.com
|
 Free | Free | For individuals starting out with automation.
|
 Emerging | Contact Us | For our customers who work with one trading partner. Fulfillment only.
|
Various alternatives pricing & plans
Lobster_data Pricing Reviews
the tool has all funktion to deploy any data conversation
Easy to use Review collected by and hosted on G2.com.
The price for the subscription is high.
not all standard interfaces (AD-connection) are included Review collected by and hosted on G2.com.
I have been working with Lobster_data for almost 10 years now and am still very satisfied. Integrations are easy to implement. To date, I have not had a case where an integration could not be implemented because of Lobster_data. The support responds quickly and is - with a few exceptions - always very helpful.
In general, it is relatively easy to work with Lobster_data. The architecture allows Lobster_data to be operated on all relevant platforms and to be connected to all imaginable source and target systems. The UI appears very tidy and clear.
The application runs very stably. In all the years that I have been working with Lobster_data and administering it in various companies, I have not had a single notable failure. Right at the beginning there was a problem with phase 4, which occurred after a patch. But here too, support provided a fix within a few hours. It is rare to see such a quick reaction to a bug, so this is definitely worth mentioning. Review collected by and hosted on G2.com.
My impression is that the company is currently expanding rapidly. My perception is that this is currently coming at a bit of a cost to support. It used to be easier to request new functions and have them provided. Today, in some situations, the impression is created that the goal is to close the ticket quickly.
Some time ago, the decision was made that the http response path in phase 6 would no longer provide detailed information about the response from the target system. This means that the response from the target system is only output in base64 encoded form. This means that a lot of added value is lost in the logs and we had to rebuild numerous profiles so that they now use phase 3 via the http function. I cannot understand why these changes were not made parameterizable so that customers can decide for themselves whether the response should be encoded in phase 6 or not. For us, this was a considerable amount of extra work and led to massive problems. Review collected by and hosted on G2.com.
