No-code databases on AWS
Collaborative structured-data tools and database applications.
3 documented options on Amazon Web Services. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.
Read this page as JSON or Markdown.
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| Baserow Self-Hosted | AWS, Google Cloud, DigitalOcean, Railway, Render, Heroku | Customer-operated Servers / containers | Open Source / Open Core MIT-licensed core with paid premium features and subscription terms | Docker, Docker Compose or official Helm chart | Customer operates the application, database and storage, applies updates and configures backups.Scope and evidenceSelf-hosting is available independently of Baserow Cloud. The core is largely MIT-licensed, while premium features need a paid license. The official AWS guide documents EC2, ECS/Fargate and EKS paths; it does not establish equivalent deployment support on every hyperscaler.
Cloud evidence reviewed 2026-11-12 |
| Grist Self-Hosted | AWS, Azure | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for grist-core; Grist Labs sells an edition with additional features under separate terms. | Run the documented Grist server container and configure persistent storage, authentication and production settings. | Customer manages authentication, access rules, document and metadata storage, backups, sandboxing and upgrades.Scope and evidenceThe listing covers the self-hosted server and its configured edition. Hosted billing features and commercial additions are not automatically part of grist-core. External widgets, integrations and AI services require separate review. Grist v1.7.22 is the first numbered release whose Docker images include Node.js 22.23.4, fixing CVE-2026-111497 remote code execution through Brotli-compressed responses, removing trust for compromised eMudhra certificate authorities, and updating vulnerable dependencies. Images pulled since October 22 already included these fixes; otherwise upgrade to v1.7.22 or later and refresh the deployed image.
Cloud evidence reviewed 2026-11-12 |
| NocoDB Self-Hosted | AWS, Google Cloud, DigitalOcean, Railway | Customer-operated Servers / containers | Source Available Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license. | Run the official Docker image with persistent storage or use its documented Compose-based server installer. | Customer manages app services, databases, access rules, secrets, backups, upgrades and any paid license.Scope and evidenceThe upstream license changed in January 2026; this is classified as source-available. Internal-tool Interfaces are a licensed feature, while AI apps have separate availability. Connected databases, AI providers and integrations can send data outside the account. NocoDB 2026.10.2 restricts shared views and dashboards to displayed fields, limits forms to their own fields, prevents Editors from reading workflow-step secrets and caps workflow webhook bodies at 1 MB. It also restores NC_SSO=oidc, requires unchanged RelayState for SAML IdP-initiated login and repairs air-gapped license refresh. Retest public shares, forms, workflow permissions and SSO after upgrading.
Cloud evidence reviewed 2026-11-12 |
Deployment evidence and category fit
Baserow Self-Hosted
No-code relational tables, views and APIs for collaborative business data; premium capabilities require the applicable license.
Self-hosting is available independently of Baserow Cloud. The core is largely MIT-licensed, while premium features need a paid license. The official AWS guide documents EC2, ECS/Fargate and EKS paths; it does not establish equivalent deployment support on every hyperscaler.
- Baserow AWS installation options ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents EC2, ECS/Fargate and EKS application deployment options in the customer AWS account. Select the documented image, persistent database and Redis configuration appropriate to the topology.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Grist Self-Hosted
Relational spreadsheet with linked tables, formulas, record views and access rules.
The listing covers the self-hosted server and its configured edition. Hosted billing features and commercial additions are not automatically part of grist-core. External widgets, integrations and AI services require separate review. Grist v1.7.22 is the first numbered release whose Docker images include Node.js 22.23.4, fixing CVE-2026-111497 remote code execution through Brotli-compressed responses, removing trust for compromised eMudhra certificate authorities, and updating vulnerable dependencies. Images pulled since October 22 already included these fixes; otherwise upgrade to v1.7.22 or later and refresh the deployed image.
- Grist Builder Edition cloud installation ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project provides its self-hosted Builder Edition VM image through AWS and Azure Marketplace. Review the selected image, edition terms and authentication setup; this is not an assurance that every Marketplace component is under the grist-core license.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
NocoDB Self-Hosted
Spreadsheet-style database interface with linked records, views, forms and programmatic access.
The upstream license changed in January 2026; this is classified as source-available. Internal-tool Interfaces are a licensed feature, while AI apps have separate availability. Connected databases, AI providers and integrations can send data outside the account. NocoDB 2026.10.2 restricts shared views and dashboards to displayed fields, limits forms to their own fields, prevents Editors from reading workflow-step secrets and caps workflow webhook bodies at 1 MB. It also restores NC_SSO=oidc, requires unchanged RelayState for SAML IdP-initiated login and repairs air-gapped license refresh. Retest public shares, forms, workflow permissions and SSO after upgrading.
- NocoDB community cloud installation methods ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream community-methods guide includes full application deployment on DigitalOcean App Platform and a Railway template alongside AWS ECS/Fargate and Google Cloud Run. NocoDB explicitly does not maintain these methods or give them first-class installation support. Review image licensing, database configuration, persistence and production requirements.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Deployment and procurement checks
- Private offers
- AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge. Provider source ↗ · Reviewed 2026-11-14
- Private connectivity
- PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service. Provider source ↗ · Reviewed 2026-11-14
- Cross-account operations
- Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access. Provider source ↗ · Reviewed 2026-11-14
- Government environments
- AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Plan this deployment
Account boundary: AWS account. Access: IAM roles and policies. Network: VPC.
Provider documentation ↗ · Guidance reviewed 2026-11-10. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.
Compare this category across clouds · Search these listings · Compare 2–4 listings