zicon35

congrats on the launch! This looks very interesting

This looks pretty interesting! Will keep it in mind in my next browser automation project.

https://revert.dev founder here.

Interesting choice of license here.

Well, ELv2 is not open source. Its source available so you should probably change that not just in the title but also in the post. It is misleading!

That being said, I think open unified APIs have a ton of promise!

It is great to see another player & clearly validates what we're building @ Revert :)

this looks awesome! Cant wait to try!

Love the idea & execution of this! It was so much fun to look back on the year on Github instead of Spotify!

Good to see you all launch on HN! I'm a founder @ https://revert.dev and we are building something similar. Competition is always good for the users.

If you like Nango, you'd love us! ;)

Congrats on the launch!

Question:

* How do you see open-source being an advantage for Formbricks when competing with other tools in the market?

Excellent suggestions. Thanks so much!

1. Agreed on this! We plan to offer this as a service along side our API offering at some point.

2. We’d be adding more authentication mechanisms soon so API tokens will be supported alongside OAuth.

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.

Hello! The platform we're building is quite generic to support these integrations.

Happy to take issues here and we could prioritise them based on the interest of our current customers/prospects: https://github.com/revertinc/revert/issues

hi, feel free to create an issue here and we ourselves could pick it up if it resonates with others as well: https://github.com/revertinc/revert/issues

Hi! Thanks for your comment.

> 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.

Not sure about your use-case but I'm happy to help and share the learnings we've had so far in the technical aspects of building Revert.

Maybe just a book a time with us or DM us Twitter and we can take it from there?

Great feedback!

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.

We launched v early tbh!

Thanks Kavir!

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

We agree on the promise for sure! :)

Great question!

We're different from n8n in the sense that we help you build native integrations with APIs and not in a no-code way.

We will help you build an integration of Slack (for eg) within your product with your users/customers, natively.

That means, your end-users or customers will not know that you are using our APIs underneath as Revert can be fully white-labelled.

We don't offer a workflow UI like n8n at all.

Happy to answer any further questions on this. Feel free to book a time from our cal if you think this could be relevant for you!

Cheers.

* vs Nango - we think they have great support for OAuth management and do support more APIs than ours on the surface (atleast at the moment).

Nango is based on Pizzly an existing OSS project which they built on top of. We're building it from the ground up.

Even though they seem to have more integrations, 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).

A few prospects of ours tried out Nango for this use-case and then came to us eventually.

* vs Merge - we'd be able to fly past the number of integrations offered by them being an OSS product especially because of community contributed integrations. Being a developer first product, open-source is the way to build the best product in this category.

Integrations inevitably have edge cases that you would run into and you as a customer might require Merge to behave in a certain way. The typical response at a closed-source SaaS company would be that its on "their roadmap", never to get back again. This holds you tightly with their roadmap velocity and you're locked into a vendor.

Being an open-source product you, the engineer, will be able to fix or add integrations right away in the worst case if nothing else. This way of operating is very powerful we think.

Also, we don't cost you an arm and a leg :)

We hear you, mate! Sending hugs :)

Happy to answer any follow ups or work with you to get your Salesforce Integration out quickly! :)

Just book a time here: https://cal.com/allenrevert/30min

1. We support Standard Objects (Accounts, Opportunities) and unify them into a simple schema for you to work with. We allow you to work with custom fields on standard objects already.

2. We also allow you to call native CRM apis without the hassle of managing OAuth if you need to. This will allow you to work with any nuances of a specific CRM or CRM instance. Checkout - https://docs.revert.dev/api-reference/crm/proxy

3. At the same time, we are launching custom object support very soon that will allow you to work with custom entities as they are but in a much better way than using the native APIs directly.

You would need to know how to use docker/docker-compose to be able to set it up within AWS/any other cloud provider.

- We're coming up with other easier ways to self-host at the same time. Our friends at Scoutflo (https://deploy-home.scoutflo.com/) & https://nuon.co/ are building something cool for this.

- We can do this as a "done-for-you" setup or be completely hands-off and give you just the docker images to go ahead with. This mostly will depend on our customer's needs and bandwidth.

1 - Two ways we ensure we're secure & private.

* We take security seriously and understand that storing sensitive information is risky. Therefore we're undergoing SoC2 Type 2 for our hosted version to ensure that we follow the best security practices ourselves in how we store data.

* If you still don't trust a third party like us you could use the self-hosted version of Revert and use it in your own infra. (we can assist you in this)

2 - The way we simplify the schemas is such that you don't have to learn the nuances of each CRM for example. (what field X is called in CRM A vs CRM B)

We ensure that you need to learn only the API schema (for example Leads API endpoint) that we offer and in the background map this to the downstream CRM (Salesforce, Hubspot or anything else).

At the same time, we ensure that you can call the native CRM APIs if you need to, without managing the OAuth or refresh of these OAuth tokens.

Happy to answer any follow ups here!

Appreciate the question!

- Yes we give you keys for test environment that you could build an integration with. Once you're happy with it, you could easily just swap out the keys in production that we give you and launch directly. Since we're an API, all the code you write to integrate with us lives within your code base. Deploying is as easy as deploying your code.

- We're all code based so everything you need to integrate with us is source-controllable and diffable. We're not a no-code/low-code solution. We're building it with the developer in mind.