What is Inboard?

Every SaaS product has to be installed, and almost no two installs look the same. The same "add our script to your site" turns into a dozen different walkthroughs once you account for WordPress, Shopify, Webflow, Squarespace, and everything in between. Documenting each path, keeping it current, and supporting customers who get stuck is a job that never ends.

Inboard is an installation guide builder that solves this once. You define what an installer has to do, and Inboard renders platform-specific, step-by-step guides inside a widget you embed wherever your customers onboard.

The Inboard model

The flow is the same for every product you bring to Inboard:

1. Define requirements once. You describe what an installer must set up — paste an HTML snippet, add a DNS record, enter an API key, run a command, and so on. You write this a single time.
2. Inboard renders a platform-specific guide. Those requirements become a clear, step-by-step walkthrough that adapts to the installer's platform, shown in an embeddable widget.
3. The installer follows the steps. They open the widget, pick or auto-detect their platform, and work through instructions written for exactly where they are.
4. Verification confirms it worked. Inboard checks that the setup was done correctly, so the installer finishes with confidence instead of guesswork.

The north star is simple: a non-technical user completes the install on any supported platform, using only the widget.

Who's involved

Inboard sits between three kinds of people:

• Customer — the SaaS owner. That's you. You configure the install requirements and own the project. Most of these docs are written for you.
• Installer — your own end user. They open the widget, follow the steps, and verify their setup. They never see Inboard's configuration; they only see a clean guide for their platform.
• Integrator — whoever embeds the widget into a page or app. Often that's also you, but it can be a developer on your team. They drop in a single script tag and pass the right values; the Configuration reference covers their options.

When to reach for Inboard

Inboard is a good fit when:

• Your product installs differently across platforms and you're maintaining separate guides for each.
• You want self-serve onboarding so customers can install without opening a support ticket.
• You need to confirm an install actually worked, not just trust that the customer followed the steps.
• You want copy-paste-ready guides pre-filled with each customer's own values.

Next steps

• Core concepts — the five entities that make up an Inboard setup and how they fit together.
• Quick start — build and embed your first install template in about five minutes.