Skip to content

Open SaaS

Open SaaS is a Wasp starter project with sample app features, sign-in and billing integration code. Wasp is the framework that builds the web app and its server from the project.

Visit Open SaaS

What runs before you connect outside services?

The local guide uses Wasp, Node.js and PostgreSQL. Its default local database path uses Docker. The guided tour says the template can start before you provide your own service credentials, but features that need those services will still be unavailable.

Check the exact version requirements and Windows setup. The guide uses a Linux environment on Windows through WSL2. Before using any local test that could send data, verify the database and outgoing services are disposable or disabled.

Which parts are yours to host and maintain?

The template is MIT-licensed and you keep an editable copy. For a live app, choose a host and database, configure the site addresses and enable only the providers your product uses. The deployment guide documents both Wasp’s deployment path and a manual option.

Hosting, payment processing and delivery services have their own terms and costs. Your team still decides who can see each record, when paid features unlock and what the app does after cancellation.

What can change when you update Wasp?

When you update Wasp itself, follow the migration guide for your current version. Updating the Open SaaS template is a separate decision. The maintainers advise against merging the entire new template into an app you have already changed. If you need a specific fix or feature, check whether it works with your Wasp version and bring over only the related changes by hand.

Keep the editable project and a record of which database changes went with it. Try an upgrade in a disposable copy and check that it can reopen a saved record before deploying it.

What would a first saved-record check look like?

Draw a fictional workshop plan in a local app. Do not install anything or connect a service.

  1. Pick the first useful result
    Sketch a signed-in person saving one draft class.
  2. Show what stays
    Close and reopen the drawing. Mark where the class should be saved and who can reopen it.
  3. Keep the exercise small
    Leave payments and outgoing mail disabled. Write what you would check before later using a test provider. No real sign-in or database was tested.