Lowdefy

Lowdefy is an open-source, config-first web stack that lets teams build internal tools and full-stack web applications using YAML that is easier to review…

  • AI
  • Development
Lowdefy is an open-source, config-first web stack that lets teams build internal tools and full-stack web applications using YAML that is easier to review than generated code.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

74/100 Good

Maintained
100last commit 7 days ago
Popular
703,026 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
3,026
Open issues
14
Last commit
2026-11-14
Latest release
v7.4.0
License
Apache-2.0
Activity
declining

Checked 3 days ago - source: GitHub (lowdefy/lowdefy)

Resources & Compatibility

Requirements not published yet.

Checked 3 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Run the built app with lowdefy start After Lowdefy is built, run lowdefy start in the finished server folder (the directory with the production files). If you skip this or use the wrong folder, the app will not come up in a browser. source
  • Keep secrets in a .env file If your setup uses secret values, put them in a .env file (a plain text file for secret settings) and reference them by name, like the SENTRY_DSN and SENTRY_AUTH_TOKEN example. This keeps tokens out of visible config and helps the app find them. source
  • Fill in login credentials before enabling auth For login providers, set the provider's client ID and client secret (the app's login identity and password) using _secret as shown in the example. Without them, the login page cannot create a session and users may be unable to sign in. source
  • Start development locally Run npx lowdefy@latest dev to start a local Lowdefy development server. source

Fetched 3 days ago - each note links to its source

Alternatives (6)

Checked 3 days ago - source: AlternativeTo

Common questions

What port does the local Lowdefy development server use?

Running npx lowdefy@latest init and npx lowdefy@latest dev creates a lowdefy.yaml in the current directory. The development server starts at localhost:3000.

Where must I run lowdefy start after building a Lowdefy app?

Run lowdefy start in the finished server folder, which contains the production files. If you skip this or use the wrong folder, the app will not come up in a browser.

How should secret values be stored in Lowdefy?

Put secret values in a plain .env file and reference them by name. The docs show SENTRY_DSN and SENTRY_AUTH_TOKEN as examples.

What must be set for a login provider before enabling authentication?

Set the login provider's client ID and client secret using _secret before enabling auth. Without them, the login page cannot create a session and users may be unable to sign in.

Which databases and services can Lowdefy connect to natively?

Lowdefy lists 10+ data connectors, including MongoDB, PostgreSQL, MySQL, REST APIs, Google Sheets, S3, Elasticsearch, and Stripe.

Answers sourced from github.com, github.com, github.com, github.com

Community

Collected 3 days ago - public community threads