bastienbeurier

7 ms·

31.
Nango (YC W23) Is Hiring a Senior Product Engineer (100% Remote, EST Timezone)(nango.dev)
1 points by bastienbeurier 2y ago
32.
Nango (YC W23) Is Hiring a Senior Product Engineer (100% Remote)(nango.dev)
1 points by bastienbeurier 2y ago
33.
by bastienbeurier 2y ago
If you are interested, we are working to solve these shortcomings at nango.dev. Instead of having a black-box unified API, you can define the schemas/interactions between Nango & external APIs, in code. Which means you can do detai
34.
by bastienbeurier 2y ago
Standard pre-built integrations are ok to get started. But rapidly customers ask for more integration capabilities, which are not supported by standard integrations. At this point, SaaS companies need to build custom integrations that fit e
35.
by bastienbeurier 2y ago
The players you mentioned pre-build standard integrations, in specific categories (e.g. HRIS). We build a platform that lets developers build custom integrations, for any API. We do offer integration "templates", but it's onl
36.
by bastienbeurier 2y ago
We've noticed the same pain point and we are providing increasingly better support for ERPs. Realistically, it takes time to build expertise on each of them, but we'll get there!
37.
by bastienbeurier 2y ago
The main difference is that Merge pre-builds all integrations, with limited customization capabilities, while Nango gives you full control over the code of the integrations.
38.
by bastienbeurier 2y ago
Yes, this works, and it's a feature we offer for free!
39.
by bastienbeurier 2y ago
Some integrations are connected at the org level (one account for the entire company), and others at the user level (many accounts per company). For the latter case, the pricing per connection is lower.
40.
by bastienbeurier 2y ago
Thank you for the insights and looking forward to chatting!
41.
by bastienbeurier 2y ago
It does! Because Nango lets you define input & output models of integrations, it's easy to standardize them across APIs. So, when syncing users from Slack/Discord/Teams, you define a standard User model, and all 3 integra
42.
by bastienbeurier 2y ago
1) That's right! 2) You can write your own integration scripts, in code, consuming any endpoint from the external API, so you are not limited to what Nango pre-builds (details: https://docs.nango.dev/understand/con
43.
by bastienbeurier 3y ago
Nango | Backend Engineers | Full-time | Remote (US/Canada East & Europe) | https://nango.dev Nango is a developer platform to build product integrations 10x faster. We’re 5 veteran engineers (Uber, Netlify), repeat foun
44.
Nango (YC W23) Is Hiring Back End Engineers (Remote)(nango.dev)
1 points by bastienbeurier 3y ago
45.
by bastienbeurier 3y ago
This looks very interesting, congrats! Do you support write-backs & workflows?
46.
by bastienbeurier 3y ago
These are all fair points! In practice, most customers we serve have use cases that could not be supported by traditional unified APIs, but are still better off not rebuilding an integration infrastructure from scratch. We also offer profes
47.
by bastienbeurier 3y ago
(Nango co-founder here) I'll update the repo readme and other mentions of being open source. Thank you for reporting this. We are not set on the license yet. We want to promote permissive usage, particularly for the auth-related featur
48.
by bastienbeurier 3y ago
(Nango co-founder here) Great. The client is just a thin wrapper around our REST API, which can be called from any language. But we plan to release SDKs for all main languages this quarter (including Java). Happy to chat on the community!
49.
by bastienbeurier 3y ago
For example, if you want to synchronize a specific object type, you would get: the authorization for the API, a helper for paginating requests, easy data deduplication, resilient background syncing, rate-limits handled, and a way to get the
50.
by bastienbeurier 3y ago
(Nango co-founder here) That's a great point. You highlight a key limitation of traditional unified APIs and one of the reasons why we started Nango. There's a lot of subjectivity that goes into unifying functionalities across API
51.
by bastienbeurier 3y ago
Ok I see. Indeed, it would be worth specifying what the boundary is in our case. Thank you for the feedback!
52.
by bastienbeurier 3y ago
Thank you! I agree that getting approved to have an OAuth app is a major pain point (for some APIs). We help customers navigate this and would like to do more in the future (partner with API providers, offer sandbox accounts without approva
53.
by bastienbeurier 3y ago
(Nango co-founder here) We use the Elastic license precisely for the reason you mention: to prevent companies from rebranding Nango and selling it as it is. For all other use cases, it should be accessible.
54.
by bastienbeurier 3y ago
(Nango co-founder here) Because there will be a lot less that you need to build. You will write less code & ship faster. You will get reporting, monitoring, alerting, a management dashboard & APIs. You will also have an integration
55.
by bastienbeurier 3y ago
(Nango co-founder here) Codat is focused on financial integrations, and Nango is transversal, so you can have all your integrations on one platform.
56.
by bastienbeurier 3y ago
(Nango co-founder here) We help teams who don't have the resources or expertise to build & maintain integrations. Sometimes, they need to build a lot, complex or scalable ones, or they want to invest their energy elsewhere. Buildin
57.
Nango.dev (YC W23) is hiring a founding back end engineer (remote)(nango.dev)
1 points by bastienbeurier 3y ago
58.
by bastienbeurier 3y ago
That's what we do at http://nango.dev
59.
Why is OAuth still hard in 2023?(nango.dev)
642 points by bastienbeurier 3y ago|282 comments
60.
Nango (YC W23) Is Hiring a Founding Engineer (full-stack/back end)(nango.dev)
1 points by bastienbeurier 3y ago

More ›