Skip to content
Sprigr

Website Hosting

Sprigr Teams includes built-in website hosting. You can run everything from a simple landing page with an embedded agent chat widget up to a server-rendered web app or a full WordPress store, without any external hosting provider.

Agents create and manage websites for you through chat — describe what you want and they generate the code, build it, and deploy it. The portal gives you a dashboard for every site with traffic, builds, domains, environment variables, and version history.

What you can host

Section titled “What you can host”
  • Static sites — HTML, CSS, JavaScript, images, and other static assets. Covers landing pages, documentation sites, and client-side apps built into static files.
  • Framework apps with server-side rendering — Next.js, Astro, and Remix projects are built and deployed with full SSR support. See Builds and Deployments.
  • WordPress and WooCommerce stores — A managed WordPress install with WooCommerce, running in its own container. See WordPress Stores.

Every website gets a URL of the form https://{organisation-slug}-{site-slug}.sites.sprigr.com, and you can attach your own domain later (see Custom Domains).

Creating a website

Section titled “Creating a website”

  1. Navigate to the Websites page

    Sign in to team.sprigr.com and click Websites in the sidebar.

  2. Click “Create Website”

    Enter a name and choose a type: a regular website, or a store (a live WordPress + WooCommerce store, set up for you in a few seconds).

  3. Choose visibility

    Decide whether the site is public or restricted — see access controls below. You can change this at any time.

  4. Optionally select a chat widget agent

    Pick an agent to power a chat widget on the site, so visitors can talk to it directly from the page.

  5. Click “Create”

    A starter page is deployed automatically, so the site’s URL is live immediately. From there, ask an agent to build out the real site, or deploy your own files through a build.

The website dashboard

Section titled “The website dashboard”

Each website’s page in the portal shows its URL, storage used, deployment count, and build minutes used this month, plus panels for:

  • Traffic — request analytics (see below)
  • Builds — build history and logs
  • Domains — custom domain setup
  • Environment — environment variables and secrets
  • Activity — a timeline of deploys, errors, and configuration changes
  • Access — visibility and per-member access grants
  • Version History — every deployment, with one-click rollback

Chat widget

Section titled “Chat widget”

When you select an agent during creation, the starter page includes a chat widget wired to that agent. Messages from visitors are delivered to the agent through a dedicated webhook, and the agent’s replies appear in the widget. The widget’s position, welcome message, and input placeholder are configurable in the website’s settings.

Access controls

Section titled “Access controls”

You can control who can view a hosted website:

  • Public — Anyone with the link can view the site. Use this for customer-facing landing pages and help centres.
  • Internal — Only signed-in members of your Sprigr Teams organisation can view the site. Use this for internal tools and documentation.
  • Private — Only the owner, admins, and members you explicitly grant access to can view the site. Manage grants from the Access panel on the website’s page.

Traffic analytics

Section titled “Traffic analytics”

Each hosted website includes request analytics, available from the Traffic panel over a 24-hour, 7-day, or 30-day window:

  • Requests — Total requests served, with a requests-over-time chart
  • Bandwidth — Total bytes served and average response size
  • Status codes — A breakdown of responses by HTTP status
  • Top pages — The most requested paths on your site

Deleting a website

Section titled “Deleting a website”

Deleting a website takes it offline immediately. Its files, deployments, custom domains, and builds are permanently removed after a 30-day grace period.

Next steps

Section titled “Next steps”