A free site to find sports/games around you (tennis, basket, chess, etc). You propose a game at a certain date/place, and people around can reach out to join. Let me know if you want to try it out (ready in the coming days).
Nango is an open-source platform that powers product integrations. It’s a developer tool built by engineers, for engineers, making it seamless to connect B2B software, natively. We serve 400+ companies with fast-growing revenues.
An app to collect memories easily. You capture vocal notes, which are transcribed & corrected with AI.
As a father, I wanted to capture all the little moments of our day-to-day family life to later share with my grown-up children. However, I did not have the discipline to journal regularly. So, I made Memzy to capture them easily on the fly!
In 2019 I made a fairly simple app that sends me an email everyday that I just need to respond to and the text of the reply gets added to a database. I have almost never missed a day since Oct. of 2019.
Some observations:
- it can be pretty hard to remember a mundane and ordinary day just 24 hours later, and after 48 hours it's usually completely gone from memory
- important or unusual events (or parties!) stay in memory a little longer
- and for me at least, food is an excellent memory anchor; if I feel lazy and don't want to add to my journal, just noting what I had for lunch and dinner will help me remembering the rest of the day much better later.
Let developers build product integrations 10x faster. Developer infrastructure / open source. Y Combinator (W23), seed stage, founded in 2022. Fully remote (Americas & Europe), 5 team members. Fast-growing revenues, 300+ companies in prod, 4.5k GH stars, community of 2k developers.
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 detailed data validation, specific to your use case, so you get back fully-typed objects. You control the data transformations to match your specific use case (so when APIs have different values for, let's say, "contact status", you define the mapping). You only sync the data you need, not full objects, so it's efficient.
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 only a way to get started and templates are meant to be extended.
That's also why our catalog of APIs is extensive. Anybody can rapidly add support for any new API and start building custom integrations for it, and share templates with the community.
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!
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.
Not trying to be snarky, but I'm not sure why this matters? Isn't the main value prop of a service like nango or Merge just the unified API and features around it (e.g. unified webhooks for events etc)? Can you help me understand why this is important?
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 exactly what they customers want.
reply