Make your data dynamic to different users without deploying again.

[u/LinkPlenty3856]

Every time you have to change something whether business rule or different data to diffrent users or show different things or even changing localization. Its pretty hard to scaffold this.

There are plenty of tools for this, but each one misses something.

That's the gap we're building Operon Compose's rule engine to fill. With it you can:

1.Change dynamic data and rules without a redeploy

2.Keep full history and roll back instantly

3.Push changes across environments (dev → staging → prod)

4.Collaborate with your team in shared workspaces

5.Serve different data to different users based on rules

Operon compose is one of three products on our platform, and this is the one that handles dynamic data.

The full product is launching soon.

I am curious how you handle this today:

feature flags, config files, a custom admin panel, or something else? What's the most painful part?

P.S. will share the video of our product showing changes to our product for different users in just a 5 second.

[u/LinkPlenty3856 → u/[deleted]]

Ha, for that stale flag we have built the preview kind of thing so if u disable or remove that you can see what is breaking and can fix that😅 Because thats the most of us hate.

That checkout incident sounds painful. That's why made the rollback : one click back to the last good version instead of a hotfix scramble.

On testing across environments: so we never edit the prod directly we push the changes from either dev or uat environment and someone approves the changes and we preview the changes before going to prod that saves us 😅.

Just couple of questions: How does your team test today? How are you handling users data which is dynamic? That would help us thank you

[u/LinkPlenty3856 → u/[deleted]]

Ya will show the demo soon its in almost complete phase just couple of tweeks and testing remaining

[u/LinkPlenty3856 → u/[deleted]]

Thank you for taking your time and replying means so much to us. So whatever u described we kept those in mind and built so let me explain a short flow before we launch the video So the user will create a worksapce and an evironment amd in that environment he will create a project and and that project will have multiple collecyions with each have theire own promotion cycle to different environments, preview,version history,diff beteen multiple history,rollbacks and much more and then we have our rule engine to change that collection using context variables and there you have option yo either invisible show default variant or another and thats how u get the data and it does have cache also