Hey HN,<p>We’re Sean and Daniel, founders of OneGraph (<a href="https://www.onegraph.com" rel="nofollow">https://www.onegraph.com</a>). We're a single GraphQL endpoint that brings together all your SaaS APIs.<p>We make it easy to build integrations for your app into services like Salesforce, Stripe, GitHub, Clearbit, and Gmail. Since each service’s API is unique you usually have to read their documentation, implement their specific authentication, make very specific calls to their servers, etc.—it seems normal right now, but all of this adds up.<p>Both of us have done plenty of integrations into these services for different startups over the years, so we knew intimately how painful it can be, especially when you have to coordinate data from multiple services.<p>Then GraphQL came along, and we saw that it could be a query language for all of the APIs we wanted. We can express our data requirements—even between services—succinctly, and let a single execution engine figure out how to translate those requirements to specific API calls.<p>We’ve built a GraphQL service that does just that - it knows how to talk to each backend API we support to pull out exactly the data you need. Here’s an example of how it works:<p><pre><code> {
youTubeVideo(id: "YX40hbAHx3s") {
snippet {
title
uploadChannel {
snippet {
title
}
twitterLinks { # twitter accounts associated with the channel
twitter(first: 5) {
tweets {
text
}
}
}
}
}
}
}
</code></pre>
(You can see the full result of the query <a href="https://gist.github.com/sgrove/5f17d046e535763c3c85258054ed00fb" rel="nofollow">https://gist.github.com/sgrove/5f17d046e535763c3c85258054ed0...</a>
or play with it yourself <a href="https://bit.ly/2NL89GA" rel="nofollow">https://bit.ly/2NL89GA</a>)<p>We charge based on the services you’re integrating with, whether you want white-label authentication for your users, and overall usage. Eventually we’ll offer an on-premise solution for bigger enterprises that need it.<p>We’d really appreciate your feedback on OneGraph. We have a lot we want to improve on, and would love to hear where you want us to go next.
In my experience one of the hardest parts of dealing with APIs is sticking within their rate limits.<p>I would expect concurrent API requests made via GraphQL to make this worse - since it's very easy to accidentally construct a GraphQL query which results in a flurry of API requests under the hood.<p>How are you handling this? Are you doing your own internal rate-limiting, or are modern APIs more generous with their limits than they used to be?
Congrats on launching !<p>Two questions:<p>1) In the example you show above, how are you figuring out which twitter accounts are linked to the channel ?<p>2) API integration is a one-time effort and largely done using libraries. Do you have a real world use case example ? My sense is most calls are isolated - for example I want to read my last few trasactions from Stripe or get last few tickets from Zendesk. Would it make sense to go through an intermediary like you and pay another monthly fee ?
Congrats! I feel like this is a modern approach to fulfilling the unrealized promise of the semantic web.<p>I've worked with a bunch of big companies and they have dozens or often hundreds of individual APIs and micro-services. Would it be feasible to deploy OneGraph in a closed environment like that? I can't think of a big IT department who wouldn't want to interconnect their internal services like that.
Here's an example OneGraph app that'll extract the captions/subtitles for a given YouTube video and let you search through them, so you can e.g. find when a term is mentioned in a talk - pure React/Apollo app!<p>Source to it is on GitHub: <a href="https://github.com/OneGraph/youtube-captions-helper" rel="nofollow">https://github.com/OneGraph/youtube-captions-helper</a><p>Try it out here: <a href="https://onegraph.github.io/youtube-captions-helper/" rel="nofollow">https://onegraph.github.io/youtube-captions-helper/</a><p>It might be fun to build a site that has transcripts for tech talks and use this to 1. bootstrap the transcript and 2. search across all talks for a term and be able to jump into the video exactly when the term is mentioned.
This kind of middleware has the potential to be as significant as relational databases.<p>Did you ever use one of those "xml data mapping" tools in your integrations?<p>If so, how would you compare their strengths and weaknesses with your solution?<p>This comparison could be compelling for enterprise customers (though your early customers will be the less risk-averse, more technical startups/small companies).
Congrats guys.<p>If this works as advertised, this is huge.<p>When I'm making API calls from my app to different services, I know for a fact that there is no extra latency that might be caused by a third-party. How do you deal with maintaining low-latency while still having to re-route my original API call?<p>Again, as someone who dealt with many APIs over the years, I think this kind of service is game-changing.
I just want to chime in with a link to a talk that Daniel gave at this year's GraphQL Europe conference: <a href="https://youtu.be/eLSWLtmzdWU?t=3m43s" rel="nofollow">https://youtu.be/eLSWLtmzdWU?t=3m43s</a> (It links to the OneGraph demo Daniel gave during the talk.)
this is an interesting idea. offhand i would have to weigh the risk of adding a (Smyte-able) middleman api vs the potential benefit of time saved having basic integrations done for me. putting a business hat on i'd say it'd be great to start with onegraph for sideprojects but once these data pipes become serious business it would make sense to invest some time bringing it inhouse. Will be interesting to see if that hypothesis is wrong; I know nothing about this market.<p>as a former product manager i could see an internal-facing product here pulling up analytics for nontechnical employees; PMs, marketers, even customer success/support. any interest in pursuing that kind of customer?
Do you plan to release the endpoint code as on premise? What's your SLA?<p>For some companies/developers (including myself), using centralized cloud services is a red flag, especially for security and for downtime.
Very cool! I actually considered building something similar myself about a year ago but got pulled into other projects... definitely see a lot of value in providing a single interface.<p>How are you planning to handle the explosion in complexity? Once you have hundreds/thousands of different services integrated, the schema becomes rather huge, especially if a specific user only needs a fraction of it. Is the plan to toggle services on/off and then only stitch the schema for a particular user with the limited set of fields?
Congrats on launching! This is really cool. How hard would it be to integrate OneGraph into an existing GraphQL endpoint that I'm already hosting to power my application?
I remember Sean showing this to me earlier this year - it's really cool to see this work in real-time. It's like magic. Congrats on launching!
1. Can you please integrate Auth0?<p>2. Can OneGraph Authentication be used for user and session management instead of Auth0?<p>3. RE: pricing, is it $24/mo for 5K/mo is ~ 1 request every 20 minutes. The next tier is about 1 request per second on average. So I guess your Individual plan is for evaluation and side-projects?
fyi running the query in <a href="https://bit.ly/2NL89GA" rel="nofollow">https://bit.ly/2NL89GA</a> gives<p>{
"data": {
"youTubeVideo": null
}
}<p>right now. did a limit bust?