We're not sure what Caspio offers to companies, but compatibility with Wordpress is not among them. We were told by their sales team that there were multiple ways, including plugins and API’s that would allow us to integrate our Wordpress site. In fact, there aren’t. For example, the limit on their API calls per month would not run our app for a day. Neither of these limitations were mentioned by their sales staff, even after repeated questioning about the costs from our CEO.
We had a fully working, functioning prototype in our old database we demo’d for the Caspio sales staff and they claimed they could match all the functionality. In fact, nearly every promise they made was specifically disproven, and, the solution seemed very limited. It’s UI features left a lot to be desired. In the end, we spent over $60k and 9 months before abandoning Caspio. We finally realized the “rathole” was simply not ever going to work. Every Caspio workaround caused another problem.
Their sole resolution was to have their technical staff work with our development team. Each time, they failed to create a reliable workaround. We finally had to walk away from tens of thousands in development costs because we figured out their routine— stonewall until their technology could catch up. It never could. And, tell us that we could upgrade (again to get “that” feature. In the end, this wasn’t true. We upgraded and still, it would not do something simple.
Caspio is good at marketing, and willing to sell you anything. But its a rudimentary, overpriced solution. We ended up with Filemaker again (our old database. It’s newer versions are substantially more compatible, and Web friendly than SAS-based Caspio. Go figure?
We were trying to use Caspio as a web-based -platform. All what we got from it, however, was buggy Eye Frames.