Thanks so much for the thorough reply, I appreciate all the info. Let me give a bit more context about what I want to accomplish.
I’m a game developer considering how I might Squidex to bootstrap a game backend. Ideally, I’d use it to create an admin and games services, including one to handle simple, turn-based game logic. Content creators would use the admin to add, remove, and edit game data like quests, NPCs, and items. That portion could make use of REST or GraphQL along with some services like getting game data, player stats, or a leaderboard. Other services like matchmaking and the game logic would make more sense as grains.
Upon looking further into Squidex further, I think I’m getting a better understanding of how it works. I thought it was more like Strapi where you create a new Strapi project and build on top of it, like creating a new project from a template, like ASP .NET Web API for example. With Squidex, you just run Squidex and create separate apps that interface with it using the Squidex client, correct?
So in my case I would deploy a Squidex instance and create my own API and Orleans app, right?