Yes. It’s like Zapier that connects various APIs together but instead of no-code blocks that marketing/sales/product teams use, we are an API itself that developers can use to build integrations that are natively coupled into your product. This way your users don’t really know that you’re using Revert
Hi! Appreciate the comment and understand the skepticism here.
Well business/startups are tough are in general & more die than survive so you're probably right on those stats.
Would love to know more about your experience specifically though? Which products did you try? What was the use-case you had that made you add your own integration?
I'd love to chat more on this if you'd be up for it. :)
Hi, our frontend logic is minimal. Most of the product is the API which can be called from anywhere.
I don't see why this may not work for your use-case too. I'm happy to chat more if you want to just talk tech here and maybe avoid engineering work for your use-case.
> Even though [Nango] seem to have more integrations
We agree Nango has more integrations and we love OSS software so I'm with you on this. Credit where credit is due and we don't want to make false claims at all. We never claimed to have more integrations than them. I'm not sure how what I posted came off as dishonest.
> but seemingly only for picking out response key if they're strings, not any "pick from object", or "compute based on multiple properties"?)
I'd say we support this perhaps in a different way.
I have not used Nango myself to comment on specific ways it handles data vs how we handle it.
Its great that you're liking Nango and we want OSS/better product to win regardless.
We're getting a few community contributions out this week into Revert in a very hands-on way.
This way we'd learn how to best optimise the product to allow for community contributed integrations at scale and the tutorial will be basis these learnings.
Our pricing is in-line with B2B customers and the way we define a connection is a single tenant (example: CRM) connecting through our APIs. Within that CRM/tenant, you could make as many API calls as you'd like (upto a certain limit). Usually this means, one connection <> one customer of yours.
If you're a B2C application with a lot more connections happy to chat more and work out a pricing that works for both of us.