@jonathacosta Thank you! Right now, this is forward only, but handling rollbacks / different versions is on our roadmap. For which use cases would you like to use such a feature?
@terencexu003 permissions are deeply integrated across every part of pylo. You can define them per tenant / customer and per user or any other entity that is linked to an user object. Permissions can be defined for both, entity and field level. APIs are not really deployed, but always auto-generated and if you are sending the user-token, you only get the GraphQL schema with those entities, queries and mutations you may actually use.
Hello and welcome to pylo!
Skip the repetitive backend work. Design your data schemas visually and get production-ready GraphQL APIs instantly — all optimized for scale and performance out of the box.
Check out the docs: https://docs.pyloapp.com/
cool
nice UI
nice work
@iptvpremiumplayer Good luck on your platform!