Most product updates focus on new features and what's working well. This one is about the other side: what Supero doesn't support yet.
For transparency, I work on Supero, a platform for generating governed, multi-tenant applications from a schema. These are the limitations I’d want to understand before choosing a platform like ours.
Database connectors:
Supero can read from external databases. Direct write-back currently works with Postgres, Supabase and MySQL.
One way sync, which would copy source data into the application on a schedule, isn't available yet either. It's on the roadmap.
It's also worth being clear about what we mean by one way sync. It copies source data into the application, but it doesn't reconcile records deleted from the source or push local changes back upstream.
Access policies:
Access policies need to be configured. Creating an entity without attaching a policy doesn't automatically lock it down, and the admin role is intentionally powerful.
That gives developers control over the policy model, but it also means you need to review the generated policies instead of assuming everything is denied by default. Deny-by-default scaffolding is something we want to add, but it isn't the current behavior.
Audit history:
We track who created or changed a record. We don't yet track who viewed it.
If your compliance requirements include read-access history, you will need to cover that separately for now.
SLA and mobile:
We have web applications running in production, but we don't publish an uptime SLA yet.
Mobile also hasn’t had the same level of real-world use and testing as web. If mobile support or a formal SLA is essential to your application, talk to us before building around it.
Free trial:
You can use the free tier to generate an application and test it end to end without entering a card.
It's meant for evaluation, though. Keeping an application hosted permanently requires a paid plan.
What you can test today:
The areas we are comfortable asking developers to test closely are tenant and role isolation enforced on the server, and field-level access that removes restricted fields from the API response rather than only hiding them in the UI.
You also own the generated code. The applications use readable Python and JavaScript, and you can download them, move them to your own repository and run them on Supero Cloud, AWS, GCP or your own infrastructure.
Our demos include test credentials and curl commands because we would rather let you test the access controls yourself than simply claim they work.
If one of these limitations blocks your use case, let us know. That feedback helps us decide what to work on next. If you find another gap that isn't listed here, we would like to know about that too.
Code and demo apps 19 MIT-licensed projects:
https://github.com/supero-platform/supero-apps
Try the builder:
https://supero.dev/?utm_source=devto&utm_medium=post&utm_campaign=honest-list
Top comments (0)