<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: rguldener</title><link>https://news.ycombinator.com/user?id=rguldener</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 30 Apr 2026 20:28:11 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=rguldener" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[The emergence of just-in-time integrations]]></title><description><![CDATA[
<p>Article URL: <a href="https://nango.dev/blog/just-in-time-integrations/">https://nango.dev/blog/just-in-time-integrations/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47922391">https://news.ycombinator.com/item?id=47922391</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 27 Apr 2026 14:51:06 +0000</pubDate><link>https://nango.dev/blog/just-in-time-integrations/</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=47922391</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47922391</guid></item><item><title><![CDATA[New comment by rguldener in "What we learned building 100 API integrations with OpenCode"]]></title><description><![CDATA[
<p>Author here, the build happens together with building your app.
Once built, the code executes deterministically at runtime.<p>The news here is the AI reading the API docs, assembling requests, and iterating on them until it works as expected.<p>This sounds simple, but is time consuming and error prone for humans to do.</p>
]]></description><pubDate>Tue, 31 Mar 2026 08:44:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=47584413</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=47584413</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47584413</guid></item><item><title><![CDATA[What we learned building 100 API integrations with OpenCode]]></title><description><![CDATA[
<p>Article URL: <a href="https://nango.dev/blog/learned-building-200-api-integrations-with-opencode/">https://nango.dev/blog/learned-building-200-api-integrations-with-opencode/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47579818">https://news.ycombinator.com/item?id=47579818</a></p>
<p>Points: 99</p>
<p># Comments: 21</p>
]]></description><pubDate>Mon, 30 Mar 2026 21:18:52 +0000</pubDate><link>https://nango.dev/blog/learned-building-200-api-integrations-with-opencode/</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=47579818</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47579818</guid></item><item><title><![CDATA[New comment by rguldener in "Ask HN: Who is hiring? (December 2025)"]]></title><description><![CDATA[
<p>Nango | Staff backend engineer | Remote | Full time | $120-200k + equity<p>Nango (YC W23) is an open-source developer infrastructure for product integrations.<p>We power the integrations of Replit, Semgrep, Motion, Vapi, Exa, and hundreds of other AI companies.<p>Small but highly experienced team, hard technical challenges (scale + infra devtool running untrusted user code), tons of ownership, direct customer contact, growing very fast.<p>We are looking for a Staff engineer who can touch every part of the stack and is passionate about dev infrastructure.<p>Website: <a href="https://nango.dev">https://nango.dev</a>  Jobs: <a href="https://nango.dev/careers">https://nango.dev/careers</a></p>
]]></description><pubDate>Mon, 01 Dec 2025 20:52:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=46113045</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=46113045</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46113045</guid></item><item><title><![CDATA[New comment by rguldener in "Workday to acquire Pipedream"]]></title><description><![CDATA[
<p>Nango is an open-source alternative: <a href="https://nango.dev">https://nango.dev</a><p>Especially if you use pipedream for integrations in your agent or product.<p>(I’m one of the founders)</p>
]]></description><pubDate>Thu, 20 Nov 2025 04:02:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=45988805</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=45988805</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45988805</guid></item><item><title><![CDATA[New comment by rguldener in "Ask HN: Who is hiring? (November 2025)"]]></title><description><![CDATA[
<p>Nango | Staff backend engineer | Remote | Full time | $120-200k + equity<p>Nango (YC W23) is an open source product: Developer infrastructure for product integrations.<p>We power the integrations of Semgrep, Motion, Vapi, Exa, and hundreds of other B2B software.<p>Small but highly experienced team, hard technical challenges (scale + infra devtool running untrusted user code), tons of ownership, direct customer contact, growing very fast.<p>We are looking for a Staff engineer that can touch every part of stack and is passionate about dev infrastructure.<p>Website: <a href="https://nango.dev">https://nango.dev</a> Jobs: <a href="https://nango.dev/careers">https://nango.dev/careers</a></p>
]]></description><pubDate>Mon, 03 Nov 2025 21:06:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=45804432</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=45804432</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45804432</guid></item><item><title><![CDATA[New comment by rguldener in "Anyone built an email or calendar assistant that syncs and indexes data?"]]></title><description><![CDATA[
<p>It varies a lot. Which is why we always recommend to start with the feature requirements/user problem and work backwards from there.<p>Examples:
- Low latency to show X last emails a person had with a specific email address<p>- Enriching data from the emails/calendar with other data from your product (E.g. mapping email recipients to contacts)<p>- Knowing when a calendar event has changed (sometimes also possible with webhooks)<p>- Detecting deletes (maybe also possible with webhooks, not sure for gmail/calendar)</p>
]]></description><pubDate>Wed, 22 Oct 2025 17:14:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=45672189</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=45672189</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45672189</guid></item><item><title><![CDATA[New comment by rguldener in "Anyone built an email or calendar assistant that syncs and indexes data?"]]></title><description><![CDATA[
<p>Founder of <a href="https://www.nango.dev">https://www.nango.dev</a> here.<p>A lot of teams use us for their Gmail & Google calendar integrations.<p>If you want to run complex queries across large parts of the data, syncing + indexing on your side will be necessary. Limits on filters, pagination & rate limits make it infeasible to search across most of a user's inbox without tens of seconds to minutes of latency.<p>But before you sync all the data, I would test if your users actually need to run such queries.<p>Both Gmail & Google Calendar have a query endpoint that searches across many fields. I would start with a simple tool for your agent to run queries on that, and expand from there if necessary.<p>Both Nango and Composio could do this for you.<p>With Nango, you would also get syncs on the same platform, if it turns out you need them.<p>Hope this helps!</p>
]]></description><pubDate>Wed, 22 Oct 2025 16:42:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=45671751</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=45671751</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45671751</guid></item><item><title><![CDATA[Lessons learned from building an infrastructure devtool]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.nango.dev/blog/lessons-learned-building-infrastructure-devtool">https://www.nango.dev/blog/lessons-learned-building-infrastructure-devtool</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45464145">https://news.ycombinator.com/item?id=45464145</a></p>
<p>Points: 24</p>
<p># Comments: 2</p>
]]></description><pubDate>Fri, 03 Oct 2025 15:33:43 +0000</pubDate><link>https://www.nango.dev/blog/lessons-learned-building-infrastructure-devtool</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=45464145</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45464145</guid></item><item><title><![CDATA[New comment by rguldener in "Ask HN: Who is hiring? (October 2025)"]]></title><description><![CDATA[
<p>Thanks for the flag, should be fixed!</p>
]]></description><pubDate>Thu, 02 Oct 2025 15:43:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=45451225</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=45451225</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45451225</guid></item><item><title><![CDATA[New comment by rguldener in "Ask HN: Who is hiring? (October 2025)"]]></title><description><![CDATA[
<p>Nango | Staff backend engineer | Remote | Full time | $120-200k + equity<p>Nango (YC W23) is an open source product: Developer infrastructure for product integrations. We power the integrations of Semgrep, Motion, Vapi, Exa, and hundreds of other B2B software.<p>Small but highly experienced team, hard technical challenges (scale + infra devtool running untrusted user code), tons of ownership, direct customer contact, growing very fast.<p>We are looking for a Staff engineer that can touch every part of stack and is passionate about dev infrastructure.<p>Website: <a href="https://nango.dev">https://nango.dev</a> 
Jobs: <a href="https://nango.dev/careers">https://nango.dev/careers</a></p>
]]></description><pubDate>Wed, 01 Oct 2025 22:09:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=45444149</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=45444149</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45444149</guid></item><item><title><![CDATA[New comment by rguldener in "Ask HN: What are you working on? (September 2025)"]]></title><description><![CDATA[
<p>Open source tools for engineers to build integrations in their products: <a href="https://nango.dev">https://nango.dev</a></p>
]]></description><pubDate>Mon, 29 Sep 2025 21:33:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=45419027</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=45419027</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45419027</guid></item><item><title><![CDATA[API Auth Is Deeper Than It Looks]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.nango.dev/blog/api-auth-is-deep">https://www.nango.dev/blog/api-auth-is-deep</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44583980">https://news.ycombinator.com/item?id=44583980</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 16 Jul 2025 16:14:11 +0000</pubDate><link>https://www.nango.dev/blog/api-auth-is-deep</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=44583980</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44583980</guid></item><item><title><![CDATA[New comment by rguldener in "MCP Specification – version 2025-06-18 changes"]]></title><description><![CDATA[
<p>We offer volume discounts on all metrics.<p>Email me on robin @ <domain> and happy to find a solution for your use case</p>
]]></description><pubDate>Thu, 19 Jun 2025 09:40:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=44316974</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=44316974</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44316974</guid></item><item><title><![CDATA[New comment by rguldener in "MCP Specification – version 2025-06-18 changes"]]></title><description><![CDATA[
<p>Agree, one MCP server per API doesn’t scale.<p>With something like <a href="https://nango.dev">https://nango.dev</a> you can get a single server that covers 400+ APIs.<p>Also handles auth, observability and offers other interfaces for direct tool calling.<p>(Full disclosure, I’m the founder)</p>
]]></description><pubDate>Thu, 19 Jun 2025 06:51:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=44316139</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=44316139</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44316139</guid></item><item><title><![CDATA[New comment by rguldener in "Show HN: Open-Source MCP Server for Context and AI Tools"]]></title><description><![CDATA[
<p>You could use Nango for the OAuth flow and then pass the user’s token to the MCP server: <a href="https://nango.dev/auth">https://nango.dev/auth</a><p>Free for OAuth with 400+ APIs & can be self-hosted<p>(I am one of the founders)</p>
]]></description><pubDate>Sat, 15 Mar 2025 06:35:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=43370490</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=43370490</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43370490</guid></item><item><title><![CDATA[New comment by rguldener in "Ask HN: Who is hiring? (February 2025)"]]></title><description><![CDATA[
<p>Nango | Remote | Hiring fullstack engineers & Entrepreneuer in Residence<p>Nango is an open-source platform for product integrations with 300+ APIs.<p>B2B SaaS use us to connect their product with all the other SaaS their customers use.
Learn more here: <a href="https://www.nango.dev">https://www.nango.dev</a><p>We are a late-seed stage, YC-backed startup and fully remote (US & EU).<p>Hiring for fullstack engineering roles (EST timezone) and an entrepreneur in residence (also EST based).<p>More details: <a href="https://www.nango.dev/jobs">https://www.nango.dev/jobs</a></p>
]]></description><pubDate>Mon, 03 Feb 2025 21:01:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=42923042</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=42923042</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42923042</guid></item><item><title><![CDATA[New comment by rguldener in "Dear OAuth Providers"]]></title><description><![CDATA[
<p>A year ago we implemented OAuth for 100 popular APIs.<p>Our experience was exactly like OP describes: <a href="https://www.nango.dev/blog/why-is-oauth-still-hard" rel="nofollow">https://www.nango.dev/blog/why-is-oauth-still-hard</a></p>
]]></description><pubDate>Wed, 11 Dec 2024 20:29:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=42392582</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=42392582</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42392582</guid></item><item><title><![CDATA[New comment by rguldener in "Devin is now generally available"]]></title><description><![CDATA[
<p>I agree. Integrations can be incredibly cumbersome if you have to learn each API from scratch.<p>There are also more flexible solutions like <a href="https://www.nango.dev">https://www.nango.dev</a><p>It handles the API-specific complexities (auth, retries, webhooks, per-customer config, pre-built templates) but allows you to implement the exact use case + data model you need.<p>It's open source/source available.<p>(disclaimer: I am a founder)</p>
]]></description><pubDate>Tue, 10 Dec 2024 21:53:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=42382002</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=42382002</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42382002</guid></item><item><title><![CDATA[Show HN: Nango Auth – Free OAuth for 250 APIs]]></title><description><![CDATA[
<p>Nango Auth is a free, source-available implementation of (O)Auth for 250+ APIs.<p>Auth with external APIs is surprisingly difficult. OAuth is a mess[0], many APIs require parameters other than an API key or access token, and platforms like Stripe or GitHub even create their own custom auth protocols.<p>We first launched Nango Auth on HN 1.5 years ago[1] when it only supported 40 OAuth APIs.<p>Since then, it has expanded beyond OAuth into an end-to-end solution for API authentication:<p>- Supports 250+ APIs[2]  and almost a dozen auth modes: OAuth 2.0, OAuth 1.0, API key, Basic auth, and a half-dozen custom formats<p>- Pre-built UI to help users pick & connect the API (including guides to find their API key and other required parameters)<p>- Automatic credentials validation on connect<p>- Secure, encrypted credentials storage & automatic token refresh<p>- Detects expired/broken access tokens<p>- Very detailed logs for quick & easy debugging<p>More than 300 companies use Nango Auth in production for their product integrations: From fast-growing AI startups (Respell, Beam, Levity) to established SaaS players (Typeform, Semgrep, Electric) and even public companies.
We also run a Slack Community[3] with 2,000+ engineers building product integrations.<p>Nango Auth is a part of Nango[4], our source-available product integrations platform. While Nango itself is a paid product, our auth product (Nango Auth) is free for unlimited use, forever. It’s our small way of giving back to the community. You can either self-host Nango Auth or use our free cloud option.<p>We hope Nango Auth can be helpful for your next integration, and look forward to your feedback!<p>Demo video: <a href="https://www.loom.com/share/e704192eb5ba42479803135db1ceccd8" rel="nofollow">https://www.loom.com/share/e704192eb5ba42479803135db1ceccd8</a><p>GitHub Repo: <a href="https://github.com/NangoHQ/nango">https://github.com/NangoHQ/nango</a><p>Landing page: <a href="https://www.nango.dev/auth">https://www.nango.dev/auth</a><p>[0]: <a href="https://www.nango.dev/blog/why-is-oauth-still-hard">https://www.nango.dev/blog/why-is-oauth-still-hard</a><p>[1]: <a href="https://news.ycombinator.com/item?id=34693233">https://news.ycombinator.com/item?id=34693233</a><p>[2]: <a href="https://docs.nango.dev/integrations/overview">https://docs.nango.dev/integrations/overview</a><p>[3]: <a href="https://nango.dev/slack">https://nango.dev/slack</a><p>[4]: <a href="https://www.nango.dev">https://www.nango.dev</a></p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=42127681">https://news.ycombinator.com/item?id=42127681</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 13 Nov 2024 16:51:48 +0000</pubDate><link>https://www.nango.dev/auth</link><dc:creator>rguldener</dc:creator><comments>https://news.ycombinator.com/item?id=42127681</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42127681</guid></item></channel></rss>