An important trend is the API-ification of everything. As more and more businesses are accessible with a web API, the Internet becomes more and more powerful.
I'd like to invite people to try the early release of Empire API, which is one API for every enterprise SaaS:
Empire is an API for accessing enterprise SaaS services such as Salesforce, Zendesk, Google Apps, etc. It provides a uniform, database-like interface to every service that it supports. Empire makes it easy to integrate data from multiple enterprise services into your own enterprise app.
You can click Login to create an account, and we'll send you an API key. Or you can just sign up for the mailing list.
I don't know if you're looking for fundraising, but if so, you have a nice opportunity here. Make it trivially easy to build investor metrics (like, I dunno, suggest queries around the tools startups are using, like mixpanel, intercom, stripe) and graphs, and then you'll be in every deck that they see.
I looked at a few companies in this space when I was at a VC, and the fundamental problem was that they didn't provide enough value to the end developer.
Aggregator APIs tend to provide extremely reduced functionality compared to the source API, and the ease-of-use doesn't compensate for this. In most cases it just makes more sense for the developer to spend a day building a custom adaptor for the API.
That said I think the SQL front-end is an interesting twist. While developers find it easier to use the source API there are many people (i.e. business analysts, etc.) who can't program but can use SQL and that might be an interesting market to go after (and also a market more willing to pay).
Thank you. The pure SQL is a cool twist, because you can instantly start getting fancy, e.g. doing JOINs between different services.
In terms of value to the end-developer, there are a handful of value-add services we'll be rolling out that are a pain for people to implement:
- Authentication
- Federated search
- ETL / caching
- Record matching / fuzzy inference of foreign-key relationships
- Entity de-duplication
We also feel that Empire API will be exciting for pure client-side apps and apps that don't want to run a backend, e.g. the sort of apps that would build on Parse or Firebase.
Very interested in your product. With Catalist[1], we are approaching each of these SaaS functions from the ground up. Integrating your product would be huge for onboarding and creating a seamless transition. Let's definitely chat[2].
neat, but SFDC alone is unbelievable ... as in i do not believe it. API limits, governors, etc. will all kill your fancy meta-api. working a lot with SFDC, an API on top of an API is simply performance hell.
co-founder here. it's a good point. yes the Salesforce API limits are still there, and you still need to work around them, but we don't make it worse.
you also get the advantage of having a datastore to conveniently persist data that you extract from Salesforce and other data sources, so that you can process data in batches easily.
I'd like to invite people to try the early release of Empire API, which is one API for every enterprise SaaS:
http://empiredata.co
Empire is an API for accessing enterprise SaaS services such as Salesforce, Zendesk, Google Apps, etc. It provides a uniform, database-like interface to every service that it supports. Empire makes it easy to integrate data from multiple enterprise services into your own enterprise app.
You can click Login to create an account, and we'll send you an API key. Or you can just sign up for the mailing list.