Show HN: Revert – Open-source unified API for product integrations

Great question -

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.

You could book a time with us, happy to chat further: https://cal.com/allenrevert/30min

Congrats on the launch folks!

i have probably seen 10 products in this space come and go in way less time than one would think both proprietary and open source. proprietary are either shut down or acquired and made unusable by price explosion or crippling of features. the open source ones always turn stale way before even half of that ambitious integration list has a checkmark, which makes these kind of a joke. relying on something like this seems to never be worth it: the painful parts are usually auth flows and maybe api paging but anything that could cause api mismatch or store data on third party servers is a recipe for disaster. in addition no integration platform i saw that was doing more than hand through the base api surface directly would cover every detail and have quite the level of feature support focus that was relevant to the application. i saw more than once that a company had to add their own app and integration just to handle unsupported cases because they could not afford a complete rewrite to add a critical feature in a timely manner.

Do you have any resources for the planning/architecting phase of developing a unified API like this?

I work in a similar space, but for physical hardware, and one challenge we've frequently encountered is the somewhat massive variety of how our vendors handle certain tasks behaviorally within their platform.

I love these kinds of products, and welcome any competition in the space. But, this comparison to Nango doesn't seem accurate, so I feel inclined to comment.

Please correct me if I'm wrong, but you say...

> Even though [Nango] seem to have more integrations

Nango has north of 100 integrations, Revert seems to have 4 atm?

> our integration support is better than them in terms of the depth of use-cases allowed (more standard objects supported, custom properties, field mapping support, custom objects (soon) etc).

How so?

Nango Sync gets you easy access to the raw API responses from the 3rd party service, and lets you map that to whatever shape/model you, as the implementer, want to end up with.

Revert seems to return standardized/normalized objects per data model (e.g, company, contact, task) across the 4 different integrations currently mentioned. It also seems to support "custom mapping" past the "lowest common denominator" schema, by adding `sourceFieldName` -> `targetFieldName` mappings (but seemingly only for picking out response key if they're strings, not any "pick from object", or "compute based on multiple properties"?)

Please don't take this as discouragement -- it's a great space to play in, and there's a lot of room for improvement. But, as a _very_ happy user of Nango over the past 10+ months, I feel you should compare yourself honestly at the very least.

Good luck!