iso27diy-corp/AuditGlue/System alternative/iso27DIY Preferred Stack.md

tags
project/iso27DIY #stack WeWeb #SupaBase

Preferred Low-Code Stack for iso27DIY

Perplexity

Key Requirements

• Low-code web app development
• Avoid vendor/code lock-in
• Minimal entry costs for MVP

Frontend: WeWeb

• Why:
  • Exports clean, customizable Vue.js code, allowing you to fully own and modify your frontend outside the platform~5~.
  • You can self-host, integrate with CI/CD, and deploy anywhere (AWS, Netlify, etc.)5.
  • Flexible integration with external backends via APIs.
• Entry Cost:
  • Free tier available; paid plans for advanced features, but MVPs can start with minimal cost~5~.

Backend: Supabase

• Why:
  • Supabase is open source, offers a free tier, and provides a scalable PostgreSQL backend with authentication, storage, and real-time features. Supabase offers Edge Functions for business logic.
  • Airtable is easy for non-developers, but for long-term flexibility, Supabase is preferable.
• Entry Cost:
  • Generous free tier for Supabase; Airtable also has a free plan.

Integration Layer

• Use REST or GraphQL APIs to connect WeWeb (frontend) with Supabase/Airtable (backend).
• This loose coupling ensures you can swap out either layer later, minimizing lock-in~4~.

⠀

Why This Stack?

• No Vendor Lock-In:
  • Exported frontend code (WeWeb) is fully customizable and can be hosted anywhere~5~.
  • Backend is open source (Supabase) or easily exportable (Airtable data).
  • Keeping backend and frontend separate via APIs further reduces lock-in risk~4~.
• Low Entry Cost:
  • Both WeWeb and Supabase offer free tiers suitable for MVPs.
  • No upfront infrastructure or licensing costs.
• Learning Curve:
  • WeWeb’s drag-and-drop interface is beginner-friendly, and Vue.js is widely documented.
  • Supabase’s dashboard and documentation are accessible for those new to backend development.

⠀

Alternative Open-Source Low-Code Platform: Appsmith

• Why:
  • Open source, can be self-hosted, and is built for internal tools and dashboards~3~.
  • No vendor lock-in, full access to source code, and usage-based pricing (even free for community edition)3.
  • Integrates with 18+ databases and APIs.
• Best For:
  • Internal tools, admin panels, and data-driven apps.

⠀

Summary Table

Stack Component	Recommended Tool	Lock-In Risk	Entry Cost	Export/Ownership
Frontend	WeWeb	Very Low	Free tier	Full code export
Backend	Supabase	None	Free tier	Open source
Alternative	Appsmith	None	Free tier	Self-hosted

Best Practices to Avoid Lock-In

• Keep your database and business logic outside the low-code platform when possible4.
• Use open standards (REST, GraphQL) for integration.
• Choose platforms that allow code/data export and self-hosting5.

⠀ In summary:
A stack using WeWeb (frontend, code export), Supabase (backend, open source), and API integration offers the best balance of low entry cost, minimal lock-in, and flexibility for a web app MVP. For internal tools, Appsmith is a strong open-source alternative~35~. 1 https://acropolium.com/blog/low-code-mvp/ 2 https://www.mintbit.com/blog/top-7-low-slash-no-code-platforms-for-building-an-mvp/ 3 https://www.appsmith.com/blog/low-code-platforms 4 https://www.outsystems.com/blog/posts/vendor-lock-in/ 5 https://www.nocodefinder.com/blog-posts/no-code-tools-export-code 6 https://impalaintech.com/blog/low-code-platforms-list/ 7 https://www.akveo.com/blog/top-low-code-development-platforms 8 https://deployd.co/blog/low-code-vs-traditional-development-cost-comparison-guide 9 https://www.linkedin.com/pulse/best-low-code-platforms-mvp-development-amit-prakash-swucf 10 https://www.appbuilder.dev/blog/vendor-lock-in 11 https://www.outsystems.com/application-development/vendor-lock-in-challenges-and-concerns/ 12 https://refine.dev/blog/low-code-tools/ 13 https://rocketdevs.com/blog/low-code-development-platforms 14 https://impalaintech.com/blog/mvp/low-code-mvp/ 15 https://www.netguru.com/blog/bubble-no-code-development 16 https://www.reddit.com/r/SaaS/comments/1fqi03v/what_are_the_best_nocode_tools_to_build_an_mvp/ 17 https://www.reddit.com/r/nocode/comments/1fp6857/suggestions_for_a_no_code_platform_that_doesnt/ 18 https://thectoclub.com/tools/best-low-code-platform/ 19 https://www.dhiwise.com/post/how-vibe-coding-compares-to-low-code-platforms 20 https://techstartups.com/2025/03/01/no-code-and-ai-coding-tools-risks-dangers-limitations-and-hidden-costs-you-need-to-know/ 21 https://vinova.sg/2025/06/03/the-cost-of-developing-an-mvp-budgeting-for-success/ 22 https://www.appbuilder.dev/blog/building-an-mvp-with-low-code 23 https://budibase.com/blog/open-source-low-code-platforms/ 24 https://www.reddit.com/r/nocode/comments/1j8oemu/the_ultimate_list_to_coding_nocode_and_lowcode/ 25 https://dev.to/kamal_deeppareek_f5bb5d8/no-codelow-code-tools-for-mvp-development-in-2025-1k3d 26 https://snappify.com/blog/best-low-code-tools 27 https://deployd.co/low-code-migration-hub/top-5-low-code-migration-strategies-for-enterprise-apps 28 https://www.jmix.io/tech-library/low-code-vs-less-code/

WeWeb for the Frontend Supabase for the Database Supabase Edge Functions for business logic Postgres functions for data-centric rules.

Programming the business logic

With a WeWeb and Supabase stack, you have several options for where to implement business logic, each with different trade-offs for maintainability, scalability, and lock-in:

1. WeWeb Workflows (Frontend)

• What: Use WeWeb’s built-in visual workflows, conditional logic, and custom JavaScript code blocks to handle simple business rules, UI logic, and API orchestration.
• Best for: UI-centric logic, simple validations, or workflows tightly coupled to the user interface.
• Limitations: Puts logic on the client side, which can expose sensitive rules and make maintenance harder as complexity grows~145~.

⠀

2. Supabase Database Layer

• What: Implement business logic in PostgreSQL using database functions, triggers, and stored procedures.
• Best for: Data validation, calculations, and workflows that must be enforced at the data level (e.g., keeping business rules close to the data, ensuring integrity).
• Pros:
  • Logic is centralized, secure, and portable (standard SQL/Postgres).
  • Reduces vendor lock-in, since you can migrate your database and functions to another Postgres-compatible host if needed~3~.
• Cons:
  • Writing and maintaining complex logic in SQL/PLpgSQL can be challenging and less flexible than using a general-purpose language~13~.

⠀

3. Supabase Edge Functions

• What: Write serverless functions (in TypeScript/JavaScript) that run on Supabase’s infrastructure and are callable via HTTP endpoints.
• Best for:
  • More complex business logic, integrating with external APIs, or workflows that shouldn’t run on the client.
  • Use cases such as checkout flows, custom validations, sending emails, or handling webhooks~2~.
• Pros:
  • Keeps logic off the client, improves security, and is more maintainable for complex scenarios.
  • Flexible: you can write logic in a modern language and integrate with any service.
• Cons:
  • Adds some operational overhead (deployment, monitoring).
  • Still somewhat tied to Supabase’s serverless environment, but easier to migrate than pure no-code logic~123~.

⠀

4. Dedicated Backend (Optional Extra Layer)

• What: Build a separate backend (e.g., with Node.js, Python, or another stack) to act as a business logic/API layer between WeWeb and Supabase.
• Best for:
  • Large projects, highly complex business rules, or when you want maximum portability and control.
• Pros:
  • Full flexibility, easy to migrate, and not tied to any one platform.
• Cons:
  • Increases development and maintenance effort; may not be necessary for MVPs~3~.

⠀

Best Practice for MVPs

• Start with Supabase Edge Functions for business logic that shouldn’t be exposed to the client, and use Postgres functions for data-centric rules.
• Use WeWeb workflows for UI-level logic only.
• If your app grows in complexity, you can introduce a dedicated backend later without major refactoring.

⠀

Summary Table

Option	Language	Lock-in Risk	Best for	Notes
WeWeb Workflows	Visual/JS	High	UI logic, simple workflows	Not secure for sensitive logic
Supabase DB Functions	SQL/PLpgSQL	Low	Data validation, calculations	Portable, but SQL-centric
Supabase Edge Functions	TypeScript/JS	Moderate	Complex, secure business logic	Good balance for most MVPs
Dedicated Backend (API)	Any	Very Low	Large/complex projects	Most flexible, most work

In conclusion:
You do not need an extra backend layer for most MVPs. Use Supabase Edge Functions and database functions for business logic, and reserve WeWeb workflows for UI-level tasks. This approach keeps your logic secure, maintainable, and minimizes lock-in while allowing for future migration or scaling~12345~. 1 https://community.weweb.io/t/recommendation-for-business-logic-using-supabase/8320 2 https://supabase.com/blog/simplify-backend-with-data-api 3 https://www.reddit.com/r/Supabase/comments/1kcm181/how_do_you_get_around_the_lack_of_a_business/ 4 https://www.nocodeassistant.agency/blog/weweb-and-supabase 5 https://www.weweb.io/integrations/supabase 6 https://community.weweb.io/t/recommendation-for-business-logic-using-supabase/8320?page=2 7 https://community.weweb.io/t/can-supabase-do-the-entire-backend-with-advanced-logic/4181 8 https://www.reddit.com/r/Supabase/comments/17c1izo/all_business_logic_within_supabase/ 9 https://www.youtube.com/watch?v=fZbkLElKuFQ 10 https://community.weweb.io/t/any-date-for-full-supabase-integration/6050

What to familiarize myself with

Summary

• WeWeb’s visual tools and
• Some JavaScript for the frontend
• PostgreSQL for the database
• TypeScript/JavaScript for Supabase Edge Functions
• Learn how to connect and consume RESTful endpoints

If you choose WeWeb for the frontend, Supabase for the database, Supabase Edge Functions for business logic, and Postgres functions for data-centric rules, here are the languages and frameworks you should familiarize yourself with:

WeWeb (Frontend)

• Visual Development:
  • Most UI and workflow logic can be built visually with WeWeb’s drag-and-drop interface~28~.
• JavaScript:
  • For custom UI interactions, logic, or integrating with APIs, some knowledge of JavaScript is helpful~25~.
• HTML & CSS (Basics):
  • While not strictly required, understanding HTML and CSS will help you troubleshoot, customize, and polish your app’s appearance~256~.
• RESTful APIs:
  • Learn how to connect and consume RESTful endpoints, as WeWeb integrates with external APIs for dynamic data~25~. ⠀

Supabase (Database)

• SQL (PostgreSQL dialect):
  • For writing queries, managing data, and especially for creating Postgres functions (stored procedures) to handle data-centric business rules~5~.
• Database Concepts:
  • Understanding tables, relationships, authentication, and permissions in a relational database context~5~.

⠀

Supabase Edge Functions (Business Logic)

• TypeScript/JavaScript:
  • Supabase Edge Functions are written in TypeScript or JavaScript, so you’ll need to be comfortable with at least one of these languages to implement backend business logic.

⠀

General Web Development Skills

• Version Control (Git):
  • Basic familiarity with Git for managing code, especially if you export code from WeWeb or collaborate with others~36~.
• Testing & Debugging:
  • Ability to test and debug both frontend and backend logic to ensure a robust application~25~.

⠀

Summary Table

Layer	Language/Frameworks	Why Learn It?
WeWeb (Frontend)	Visual builder, JavaScript	UI building, custom logic, API integration
	HTML, CSS (basics)	Troubleshooting, advanced UI customization
Supabase (Database)	SQL (Postgres)	Queries, data modeling, Postgres functions
Supabase Edge Functions	TypeScript/JavaScript	Secure, scalable backend business logic
General Dev Skills	REST APIs, Git	Integration, code management, team collaboration

In summary:
You’ll primarily work with WeWeb’s visual tools and some JavaScript for the frontend, SQL/Postgres for the database, and TypeScript/JavaScript for Supabase Edge Functions. This stack minimizes lock-in, is approachable for new developers, and leverages widely-used, well-documented technologies~25~.

1 https://www.nocodeinstitute.io/nocode-jobs/weweb-developer 2 https://www.weweb.io/blog/front-end-design-guide 3 https://www.reddit.com/r/webdev/comments/10ve6j2/what_skills_should_a_front_end_web_developer_have/ 4 https://careerfoundry.com/en/blog/web-development/frontend-developer-skills 5 https://unicoconnect.com/careers/weweb 6 https://www.merixstudio.com/blog/10-skills-need-be-frontend-developer 7 https://skillcrush.com/blog/skills-to-become-a-front-end-developer/ 8 https://www.weweb.io/blog/no-code-web-app-guide

Learning JavaScript

• Mozilla Developer Network (MDN) Web Docs: Excellent and comprehensive JavaScript guide.
• freeCodeCamp: Interactive courses that teach you programming fundamentals.
• The Odin Project: A full-stack curriculum that starts with JavaScript fundamentals.
• Codecademy: Interactive lessons for foundational concepts.
• "Eloquent JavaScript" by Marijn Haverbeke: A free online book (more challenging, but very thorough).