IBM® webMethods offers a hybrid, enterprise-grade integration platform as a service (iPaaS) that allows users to securely control applications, APIs, B2B and files across environments and locations.
$2,500
per month
Zoho Creator
Score 8.1 out of 10
Mid-Size Companies (51-1,000 employees)
Zoho Creator is a low-code application development platform for building enterprise-class applications that run on mobile, tablet, and web. It is designed to allow users to create custom forms, configure workflows, build pages, and deploy apps quickly.
$12
per month per user
Pricing
IBM webMethods Hybrid Integration
Zoho Creator
Editions & Modules
IBM webMethods Hybrid Integration Standard Tier
$2,500
per month
Standard
$12
per month per user
Professional
$30
per month per user
Enterprise
$37
per month per user
Offerings
Pricing Offerings
IBM webMethods Hybrid Integration
Zoho Creator
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
Add-ons:
Customer Portal: $100/month onwards
Premium Support : 20% of license fees
Enterprise support: 25% of license fees
In any scenario where a distributed enterprise IT landscape needs a unified approach to solve the challenges of enabling a common information supply chain where different stakeholders as well as citizen developers can be empowered to contribute, participate and own their own parts of the integration landscape - IBM webMethods offers a capable, architecturally sound and cost efficient way of supporting a wide range of enterprise system integration needs.
If you are using some application of Zoho and want some more functionality into it, Use Zoho creator to develop a separate app as per requirement and integrate it with your Zoho App. Small organization can use creator to make apps but it can be used for small range of storage, For Large organization , it may be not feasible.
In C6, the new setup of permissions is not logical. Admins now have access to every application rather than specific applications, which impacts data confidentiality.
In C6, the new feature for having multiple environments is very limited as it does not work for ZOHO Creator applications that are linked to other Zoho Creator applications in the same workspace - which is not logical at all.
In C6, the revised permissions for Developers do not allow the developer to assign permissions to users or to publish forms, reports, pages, etc....which again is not logical.
The webMethods platform is a fantastic tool for modernizing information systems. It's easy to use and delivers rapid results.The platform is focused on innovation and is accelerating its improvement with the acquisition by IBM.
Today Zoho Creator is included in our current plan from Zoho One, but if it was needed to pay apart it should be done because the software we created became very important for our team. The use of Zoho Creator contributes to endorse the Zoho One subscription year after year.
The webMethods product has a very user-friendly and easy-to-use interface.A weak point is the My webMethods Server portal (administration and monitoring portal for the on-premise platform). This weakness has been addressed thanks to the control plane on the hybrid version of the product. This version should be highlighted and used to ensure a very fluid and functional interface.
Its quite easy if one has the need, interest and passion to build applications and solutions through low-code. One example would be, that my finance head who has absolutely nothing to do with tech and apps, is now able to create apps and manage Zoho Creator all by himself. So its all about the interest and how much time we put to learn the tool. Having said that, its quite easy to learn the tool and create anything that's within our scope of knowledge.
The webMethods platform is very stable and does not cause incidents: if it is well configured and tailored at the base. Infrastructure incidents represent 20% of incidents (full disk, memory peaks, etc.) 80% of incidents come from the implementation of the code in the platform. If a code is not optimized and a high volume is observed in production, this can cause incidents. Similarly, if all error cases or conditions are not handled in the code, this can cause errors. Finally, there can be common errors if the applications connected to the platform do not return quality data or are unavailable.
In an earlier comment, I mentioned Zoho's excellent uptime. I have been using the system for over 6 years, and have experienced only momentary outages, and of those, only a hand full over the years. It is extremely reliable
The webMethods platform is designed to handle a high volume of small messages. It's a tool for continuous processing.The incidents I've seen involving application performance declines are caused by: - Code optimization issues - File size issues or fragmentation of the transmitted file - Misuse of the platform (batch processing) - Monitoring data was not purged, and the user was working with millions of data points
We do not integrate Zoho with other systems at this time, but rarely are searches, database exports, record edits or creation tasks ever slow enough to notice. It is quite usable
In the majority of the tickets I've created, support has been very responsive and provided the right solutions or solutions.Resolving a ticket also depends on the information provided by the creator. It's important to provide the technical context and information about the environment, as well as information to help the support team reproduce the incident.
I recommend Zoho Creator very often. A lot of companies go big earlier than they need to and spend way too much on SalesForce & Marketo. I worked for a small company with some limited budget that pivoted to sell it's product to the Enterprise. Zoho Creator was incredibly easy to set up, intuitive to use, and contains all the most essential features that most users need and seek in SalesForce. We integrated with MailChimp & Unbounce and were able to be incredibly useful in acquiring leads, nurturing them, and tracking pipeline in Zoho Creator. Our small sales team found it very easy to use and loved it.
We received in-person training from the webMethods team. We received standard training from the vendor and custom training on specific security topics.The training sessions went well but remained very standard and did not adapt to the client's specific business. In-person training is more suitable for rapid skill development. It is necessary to practice for a few weeks to ensure familiarity with the tool.
I found clear and easy-to-follow training with realistic use cases for quick understanding and a 360° view of the features. The lesson format allows you to progress and learn by breaking down the allocated time.The technical courses are described step by step, allowing you to quickly get to grips with the products
When implementing webMethods, it's essential to have the right support and guidance.It's important to map out the interactions, document them, prepare test cases, and implement them while making maximum use of the product's native features.Additional tools must also be planned to automate deployments, visualize logs, and monitor the platform.
Even if it is a easy to use platform, it got some issues on the implementation that could easily handle by IT teams. In our scenario this team don't exist anymore, and the business/marketing team had their expectations that it was quickier to be implemented. So, consider a professional help on this implementation could be cost more (of cource) but it would be helpful to manage the issues and expectations.
webMethods.io IntegrationDescriptionWe uses webMethods.io Integration to solve some of our application to applications and business to business integration needs. It is the Integration Platform as a Service solution that we use in a mix with our continued use of webMethods Integration Server and Trading Networks on-premises. For any solutions that meet the use cases that we deem an appropriate fit for running in the cloud, we build those solutions using webMethods.io Integration. More specifically, we use webMethods.io Integration to synchronize changes in one application or system, in another application or system, by shipping data mutations via integration messaging and API calls. We also use webMethods.io Integration to integrate with external organizations. Our trading partners and supply chain partners provide APIs that we consume, and vice versa, to notify each other of business process events as they occur in the respective organizations. Please provide some detailed examples of things that webMethods.io Integration (webMethods Integration Cloud) does particularly well. Easy to usePriced competitivelySupports robust and resilient integration solutions please provide some detailed examples of areas where webMethods.io Integration (webMethods Integration Cloud) has room for improvement. These could be features that are hard to use, missing functionality, or just things that you'd like to see done differently. Complex logic is hard to understand in a simple diagrammatic user interface too simplistic for solutions that are complicated or go against the gain runtime observability could be improved please describe some specific scenarios based on your experience where webMethods.io Integration (webMethods Integration Cloud) is well suited, and/or scenarios where it is less appropriate. We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios. What positive or negative impact (i.e. Return on Investment or ROI) has webMethods.io Integration (webMethods Integration Cloud) had on your overall business objectives?webMethods.io Integration is a cost-effective approach to integration in isolationwebMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costswebMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic AppswebMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used describe how webMethods.io Integration (webMethods Integration Cloud) stacks up against them and why you selected webMethods.io Integration (webMethods Integration Cloud). For any organization which is already using Software AG products on-premises, such as webMethods Integration Server and Trading Networks, or Universal Messaging, evaluating and using webMethods.io Integration is the path of least resistance. It will be incredibly easy for your webMethods team to get up to speed on how to use webMethods.io Integration, and start developing new solutions on it. However in my opinion you should only add cloud to your integration product portfolio if you believe you can move 100% of your integration needs to the cloud. Otherwise, you will need to maintain an on-premises integration solution anyway, which means you end up with a more complex IT landscape by adding cloud to supplement on-premises integration for little benefit in terms of cost, complexity, and resourcing requirements. For organizations that are not already a Software AG shop, you should evaluate webMethods.io Integration on its merits, however, it's usually the right decision to double down on your existing products and vendors if you have no big issues with the current state. This is to say that if you are a Microsoft shop then adding Azure cloud products to your portfolio is pretty much inevitable, and avoiding the complexity of multiple clouds should also be something organizations consider.
Zoho Creator stands out for its balance of affordability, ease of use, and powerful customization options. While it may not offer the same level of enterprise-scale features as platforms like OutSystems or Mendix, it provides a robust solution that meets the needs of many businesses, especially those looking for an integrated, cost-effective low-code platform with strong support for both simple and complex applications.
Zoho is incredibly versatile. Much thought was put in to the way the platform functions. I've yet to face a situation where Zoho would not be able to do what I needed. That being said, because of its power, it can also be a bit intimidating technically. Simple needs are simple. More complex needs are ... more complex! Overall, it's a powerful, robust platform
With using Zoho Creator we are able to build apps that we may otherwise pay a pretty penny for. We may risk some features we could get from a 3rd party app but the fact that the data we do collect can easily syn with our CRM and Accounting systems makes up for this.
Negatively speaking, it takes time to fine tune and really craft your application. I am not a coder, nor do I have a coding background, so patience is key as you design and build out your application.
