A few oddities caught my eye, though, e.g. duplicates of the edited field were created when leaving the field panel.
Is there a plan to add a feature to export the API in a standard like OpenAPI?
Lock-ins have been our biggest concern here at Canonic. We wanted to ensure that if the user wanted to move/integrate with different services, that experience be as seamless as possible. We are exploring both OpenAPI and GraphQL schema export options. Definitely on the roadmap!
Now THAT is worth me paying for! I'm now really looking forward to learning about your pricing, as I'm quite interested in using your platform. All the best!
Faced an issue creating column in a new model - Can't click on any of the button in image  (I'm on Mac & Firefox if that helps)
We are in similar space & open source : we automatically generate REST & GraphQL APIs automatically on any Microsoft SQL Server, Postgres & MySQL databases. Do give us a try. https://github.com/xgenecloud/xgenecloud
 : https://imgur.com/efPfFRx
We have been experiencing some issues on Firefox, should get sorted in the next 24 hours.
XgeneCloud looks slick! Will definitely give it a go, thank you for sharing it across
The app is a bit buggy and features are relatively sparse, but it is intuitive to use and I can see the promise.
Within 20 minutes, I had an API structure fairly well plotted out, along with REST endpoints, a GraphQL schema and playground, documentation, and places to add webhooks (although no way to programmatically add webhooks easily, as far as I could see).
I may be over-rating this simply because it comes at a good time for me - I recently spent hours reading through the JSON:API specification , and trying to figure out how it is different to the OpenAPI specification , and how to actually get into implementation, and generally getting bogged down in levels of detail that I never knew existed.
The only fear I have with this service is that the pricing structure will be too high. I would be keen on a usage-based pricing model based on amount of data stored, with a free tier for personal projects.
This would allow me to play around with it myself for free, while internal business tools with higher usage would be paid.
Interested in talking about what pricing may turn out to be - if you want to get in touch, my email address is on a feature request I submitted about adding a datetime field.
(edit to remove extraneous character, in the process adding lots more extraneous characters)
I've personally gone down that rabbit hole as well, especially when you're looking to get started quickly.
As for the pricing, our plans are to make it usage based. The goal is to have an unlimited time free-tier (with reasonable usage restrictions) along with paid individual/team/enterprise plans.
Unfortunately, our system was having some issues, so we missed out on your feedback, I'd be really grateful if you could drop us an email at firstname.lastname@example.org and we can take the conversation forward!
I like Airtable for rapid prototyping and small data stores. It seems like this would be more comprehensive for that use case? Unclear on how to approach user login and permissions (of the project and not the canonic platform)
Airtable is amazing and ️ fast for smaller projects, however like you mentioned, we want to be more comprehensive and scalable. One big differentiator there is that we support adding custom endpoints and APIs that can include custom business logic as well.
We realise the documentation is a bit sparse around auth login and permissions. I'll make sure the documentation is updated soon for the same with a guide and examples.
Thank you for your feedback!
It's a snappy admin UI and I love the auto-generating docs. All around excellent job!
I'm so glad you liked it and thank you so much for your feedback! We are working very hard to ensure that the onboarding is smooth and the learning curve flat :)
* Complete no code - Bubble
* Out of the box code - Next.js etc.
* Code - Node JS / Express etc.
Where do you fit in? Who chooses you over the other options?
Because the disadvantage of yours is lock-in / pricing / up-skilling to a non-standard way. Same problems as many others - Bubble.io etc.
There must be some killer win you get from using this.
Bubble lets people who have never coded build a rough MVP, maybe get some orders, so I can see why people fork up the $ and struggle through that UI, because the alternative is a 4-5 figure fee from a freelance programmer.
But I don't think Canonic avoids code as you still need to do the front end. (Maybe that's it? You create a front end version of Canonic next?)
So I'm interested in who will buy this and why.
Out of the ones mentioned, we are probably closest to Bubble. However, as you rightly said we are currently focused on the backend API building problem.
As we've been pivoting to be a more citizen-first non-tech friendly platform, frontend on Canonic is something we have been discussing and debating frequently.
The main concern with a frontend builder for us is the need for it to truly be as close to a design tool as possible. The frontend of an application frequently ends up being unique to accommodate branding and creative freedom and becomes hard to fit in a traditional drag-n-drop tool. We just want to make sure, we are truly solving that problem and not just making another frontend builder that people have to wrangle to get their designs to fit.
As for lock-in, we do want to avoid it all costs and our working on strategies and features that would allow you to migrate in and out of Canonic with ease.
Currently, Canonic is a great fit for anyone who wants to build a backends quickly and without writing code. Some level of technical know-how is, however, required. We do hope to eliminate that soon.
P.S. Canonic plans to have a free forever plan for getting started and hobbyist projects
We feel that currently, the learning curve is pretty minimal. Given the hours it'll save one from coding, maintaining and bug fixing. However, we will definitely keep this in mind when thinking ahead.
Thank you so much for the feedback!
I've never heard "solution" used as a verb before. It reads rather odd to me, but the product seems interesting :)
The documentation is based on Gatsby!
The vision is to reduce the complexity (and terminology) down to a point where one would need no prior knowledge of engineering to actually apply their business logic. We’ve been slowly pivoting towards citizen first development and the goal is to get there sooner or later!
Hasura on the other hand, I feel offers a superior developer experience but that comes at the cost of alienating non-technical/citizen developers. Backend knowledge still plays a pivotal role in how well you can use Hasura.