The web presence for NetSuite businesses — built, run, and out of the way.

SuiteSite builds and runs the websites and customer portals of small Canadian companies on NetSuite. We own the boring parts — speed, uptime, NetSuite sync — so your team owns the interesting ones.

What we ship

A working website and customer portal, kept that way.

No roadmap pitch. Every line below is in production today for our first customer — and the same stack is ready for the next one.

01

Customer-facing site

Fast, mobile-first storefront. Real product pages, real cart, real checkout. Hosted on your own domain.

02

Self-serve portal

Customers sign in to see their orders, invoices, wishlists, and account info — pulled live from your NetSuite.

03

NetSuite, the source of truth

No duplicate inventory system. No nightly batch jobs to babysit. The website reads NetSuite through a thin adapter; writes go back the same way.

04

Always-on operations

Heartbeat health checks, version drift detection, one-click rollback, canary rollouts. We get paged; you don't.

Principles

Boring is a feature.

Modern web stacks love to ship features you'll never use. We do the opposite. Every SuiteSite tenant is built from a small, fixed template — same components, same patterns, same failure modes.

When something breaks, we know exactly where it broke. When you want a change, we know exactly where it goes. That predictability is worth more than a longer feature list.

  • Static-rendered where possible, dynamic where it has to be.
  • One process per tenant — debuggable, restartable, replaceable.
  • Caddy terminates TLS; no nginx configs to drift.
  • NetSuite gets one read RESTlet and one write RESTlet. Minimal surface.
$ suitesite status suitesite.ca
→ HTTP 200, 47ms
→ version: 0.1.0 (latest)
→ netSuite reachable: true
→ drift: none
→ last incident: 12 days ago
→ provisioned: 2025-08-04
$ suitesite rollback suitesite.ca --to 0.0.9
→ rewriting template_version… ok
→ restarting portal@Suitesite.service… ok
→ rollback complete. uptime preserved.
How a new customer comes online

About three weeks from first call to first order.

No discovery deck. No "phase 1 of 5." One short scope conversation, then we build.

Scope call

30 minutes. We map what your customers actually do online, and what we can reuse from NetSuite instead of rebuilding.

Stand up the tenant

We register your domain, connect NetSuite, deploy the template version of the site. Usually live within a week.

Brand + content

Theme, copy, product copy. You send assets; we wire them in. Two rounds of revisions baked in.

Run it

We monitor. You sell. Quarterly reviews to roll template upgrades; no surprise invoices.

1
production tenant
shipping orders today
12mo
uptime on the
reference deployment
<100ms
p95 page load,
customer-facing pages
2
NetSuite RESTlets
total. Minimal surface.
About

The shape of the company, on purpose.

SuiteSite is a one-engineer shop backed by Scott Brien, a Canadian NetSuite partner who has been building for the SuiteScript ecosystem for over a decade. The "platform" behind SuiteSite is a small Django orchestrator that runs each customer as an isolated process — same FastAPI backend, same React frontend, same Caddy vhost — so every new tenant costs roughly the same to keep running.

The model only works because we say no to most features. If you need a marketplace, a multi-warehouse routing engine, or a configurable checkout flow, SuiteSite is the wrong product. If you need a website that loads quickly, syncs with NetSuite, and stays up while your team focuses on customers — it's the right one.

We sell by referral. We'd rather undersell and over-deliver than the reverse.

— Tristan, SuiteSite · Kitchener, ON

If that sounds like what you're looking for, let's talk.

One email, one short call, one written estimate. No pressure.

hello@suitesite.ca →