A SaaS project template with places for sign-in, payments and AI providers, plus PostgreSQL and Redis, brought up with Docker Compose on your own machine; the demo data uses a placeholder payment gateway and needs no outside accounts. A frozen snapshot of an MIT-licensed open-source project; the delivery includes an orchestration file (database and cache images fixed by digest, port bound to 127.0.0.1), a script that generates the database password, and a quick-start guide.
Developers and small teams who want to see what a SaaS project with sign-in, payments and AI features looks like on their own machine, for evaluation or as a starting template.
$ sh scripts/quickstart/init-env.sh $ docker compose up -d --build
Files in the product repository at the pinned commit. A few house files are left out of the zip.
Clone → Checkout → Toolchain → Web up and serves
A SaaS project template with places for sign-in, payments and AI providers, plus PostgreSQL and Redis, brought up with Docker Compose on your own machine; the demo data uses a placeholder payment gateway, so seeing the screens needs no outside accounts.
Derived from an open-source project under the MIT licence, and not the original project itself. Our work: an orchestration file, a script that generates the database password, and a quick-start guide.
Delivery is a frozen snapshot: one zip, taken from the product repository at revision 12e9c8b.
docker compose down -v deletes all of itThe liability cap, the scope of what is promised and the statutory floor are governed by the Terms of Service.
Everything below was checked against the pinned commit 051065c. Every verdict carries its full reasoning, an evidence link and the checker; failures are published, not hidden — do not take our word for it, verify it yourself.
3 PASS2 WARN0 FAIL
Read: docker-compose.yml (port published only on 127.0.0.1, database and cache images fixed by digest, startup refused when the database password is missing), scripts/quickstart/init-env.sh (generates a random password) and Dockerfile.demo (the build steps). The upstream source was not read file by file.
The script on the buyer path was read line by line: init-env.sh runs on the buyer host and only writes .env. Dockerfile.demo installs packages with pnpm from a lockfile at build time and runs the demo start script inside the container; what the packages and that start script do was not inspected.
This product is a frozen snapshot and does not follow upstream: the upstream source is pinned to the revision recorded in the product repository (see the evidence link). How recently upstream has been active was not checked.
SPDX:MIT
The LICENSE file in the product repository was read: the MIT text with the upstream copyright line, and PRODUCT.md and ATTRIBUTION.md record the same licence for upstream. The evidence link points at the upstream file at the pinned revision; it was not compared byte by byte with the copy in the product repository from this environment.
This records the declared side, not a scan result: dependency packages are fetched by the buyer at build time and the database and cache images are pulled from their registry, and their contents were not scanned for licences. Upstream has no submodule and no third-party dataset was copied in (see ATTRIBUTION.md).
Last verified passing: 2026-11-12
A subscription unlocks the whole catalogue; you do not buy this one separately.See what is included
Sign in with Google first; if you are signed out you will be sent to the sign-in page. Your subscription is billed to that same email address.
Already subscribed? This downloads straight away. Otherwise you are sent to the pricing page, or to sign in first.