nirga

I love flagsmith! I just commented below that I think what makes what we’re doing different is the focus on SaaS and costumer features - so which features are enabled for whom based on the pricing tier they’re at.

Great points! I think the main differentiation for us is the connection to pricing and billing. Let’s say you have a feature like “how many seats (users) this customer has” it’s not enough to just be able to define it and fetch it where’ve you need it - which is basically what the tools you mentioned will give you. It depends on which pricing tier the customer’s in. Maybe they bought 5 seats but then 2 more as an add on on top of it. Maybe you want to allow them to use more seats, but just bill them accordingly.

Does it make sense?

Huh cool thanks I didn’t know that! I guess it’s just another action and not something “native” to Zapier (so if you want to later connect it to some off-the-shelf action you can’t).

At first I thought that a code alternative for a no-code solution like zapier was counterintuitive. But as an engineer using Zapier (for the first time) these past few months I got so frustrated by the lack of an option to just write some "if" or just 2 lines of code to make things work the way I want them.

I think trigger.dev nails it. This is exactly what I needed.

Is it possible technically? I mean can you read notifications from other apps without the respective app’s API key?

Not exactly, cause you need to manage state or something (you don’t want to reprovision every time you run the code probably). So you’ll need to do some sort of “compilation”

Not exactly, Pulumi is more like CDK. So code and infra provisioning is still separate

Nice work on both refine and mantine! I’ll definitely be using it for our next project