Hey patrickaljord - it's a great question. 8base and the tools you mentioned meet at very similar cross-roads, we all take VERY different paths to get there. I think what notably sets us apart is the developer experience in defining data-model/roles/permissions/authentication/etc. through the management console. Also, 8base being a service that's production-ready as soon as you click "Create Workspace" is a big difference. I'd love for you to try building a little experimental app on 8base, and hearing what you think are the differences/similarities :slightly_smiling_face: let me know if you're interested. Thanks, Albert.

Think the major difference is that there's much less vendor lockin with 8base. 8base is just a GraphQL endpoint, letting you use any library you want to interact with it, while Amplify requires you to use their specific APIs with their infrastructure. 8base also has a built-in roles and access management system, and lets you do authentication with any OpenID connect service.

Amplify is 'just' graphql too. That's a disingenuous argument. Ironic even because 8base is all aws services bolted together.

having worked with both I think each lends itself better to different projects. Amplify gives you the option to work both with REST or GraphQL, however you then have to go through all the steps of setting up a CRUD api. That part comes out of the box on 8base, with things like relational filtering, pagination, etc.