flowershow
Flowershow is an open-source markdown publishing platform that converts markdown files into hosted websites, docs, and knowledge bases. It integrates with Obsidian, supports a CLI for AI agents, and is built with Next.js and TypeScript.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | flowershow/flowershow |
| Owner | flowershow |
| Primary language | TypeScript |
| License | AGPL-3.0 — OSI-approved |
| Stars | 1.1k |
| Forks | 121 |
| Open issues | 99 |
| Latest release | @flowershow/[email protected] (2026-06-23) |
| Last updated | 2026-07-07 |
| Source | https://github.com/flowershow/flowershow |
What flowershow is
A TypeScript/Next.js monorepo (Turborepo + pnpm) that provides a web app, Go CLI, remark plugins, and Cloudflare Workers for markdown processing. Uses Postgres, MinIO, Inngest, Typesense, and includes E2E testing via Playwright and unit tests via Vitest.
Get the flowershow source
Clone the repository and explore it locally.
git clone https://github.com/flowershow/flowershow.gitcd flowershow# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires Node.js 22+, pnpm, Docker, and PostgreSQL for local development; production deployments need Cloudflare Workers and S3-compatible storage.
- Monorepo architecture (Turborepo) means dependency on multiple interdependent packages; changesets required for versioning and npm publishing.
- Pre-commit hooks (Husky) enforce linting and formatting; biome for packages, ESLint for web app; ensure CI/CD pipeline matches local linting rules.
- Development workflow uses staging → main branch model with squash merges; feature contributions require coordination and PRs may take time to merge.
- E2E tests require test-site submodule (git clone --recurse-submodules); omitting it may break test suite.
When to avoid it — and what to weigh
- Proprietary/Commercial Product Licensing — AGPL-3.0 requires derivative works to be open-source and source-available; commercial use of modified code requires careful legal review or license negotiation.
- Minimal Operational Dependencies — Production setup requires Postgres, MinIO (or equivalent S3), Inngest, Cloudflare Workers, and optional Typesense; not a static-site-only solution if you need managed services.
- Established Enterprise Support Contracts — Project is community-driven with no stated commercial support, SLA, or enterprise license option. Unknown for critical production use requiring vendor backing.
- Low Code/No-Code User Base — Developer-focused platform; lacks no-code UI for non-technical users; best suited for teams comfortable with Git, markdown, CLI, and REST APIs.
License & commercial use
Licensed under AGPL-3.0 (GNU Affero General Public License v3.0). Requires source disclosure and open-source release of derivative works or modifications used over a network.
AGPL-3.0 imposes source-availability obligations on network-accessible modifications. Using Flowershow unmodified for SaaS or internal publishing is likely permissible; modifying and deploying the core platform requires careful license review. Requires legal counsel before commercial product licensing.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
AGPL-3.0 requires network-accessible source disclosure; no security audit details provided. Uses Postgres, MinIO, Inngest, and Cloudflare Workers—security posture depends on infrastructure configuration. No stated vulnerability disclosure policy or security contact. Requires review before handling sensitive data.
Alternatives to consider
Docusaurus
Open-source React-based static site generator with strong documentation ecosystem; MIT licensed, no source-disclosure requirements for derivatives, simpler deployment.
Obsidian Publish
Official Obsidian vault publishing service with managed hosting, no DevOps required, no AGPL restrictions; trade-off: less customizable, vendor-locked, requires subscription.
MkDocs / Material for MkDocs
Python-based markdown documentation platform; simpler setup, BSD/MIT licensed, strong template ecosystem; fewer AI/CLI integrations but mature and widely used.
Build on flowershow with DEV.co software developers
Evaluate Flowershow for internal docs, knowledge bases, or AI-driven publishing. Review AGPL licensing requirements and infrastructure dependencies before production use.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
flowershow FAQ
Can I use Flowershow for a commercial SaaS product?
What is the learning curve for developers?
Is there a managed hosting option?
Can I extend or customize the markdown processing?
Software development & web development with DEV.co
From first prototype to production, DEV.co delivers software development services around tools like flowershow. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source cms and beyond.
Ready to Publish Your Markdown?
Evaluate Flowershow for internal docs, knowledge bases, or AI-driven publishing. Review AGPL licensing requirements and infrastructure dependencies before production use.