Longeron

For teams that publish to ServiceNow Service Portal

Marketing ships its own portal pages. And cannot ship them broken.

Longeron is where communications and marketing teams lay out branded landing pages for Service Portal, with accessibility checked before anything goes live, and publishing that never asks a developer.

Talk to us See how it works
The Longeron builder. On the left, a site with its pages listed. In the middle, the Meridian Fiber campaign page as a visitor would see it: a photograph of a street at dusk with a fiber spool, the headline Fiber is coming to your street, and two buttons. On the right, the page's address, title, and description ready to edit. The status bar reads Passes the gate.
The new page dialog in the builder: seven starting points shown as pictures, from a blank page to campaign, service, and terms pages, each with a photograph of the finished page and a line about what it contains.

Start from a page, not a blank canvas

Every new page starts from a picture of a finished one. Pick the campaign, service, or terms page that is closest, then change the words and the photographs. The sections are already laid out and already pass the gate.

  • Heroes, banners, cards, price grids, terms, and more: sections, not code.
  • Photographs come with alt text or are marked decorative. There is no third state.
  • Rename a page and every link to it follows; the old address keeps working.

The middle step cannot be skipped

Before anything reaches your instance, Longeron compiles the page and checks the result against WCAG 2.1 AA, the same page visitors will get. A page that fails does not publish. This is not a linter you can dismiss.

  • One heading, no skipped levels, real link text, described images.
  • Brand colors are checked as pairs, on every surface, as you type.
  • Every link to another page must resolve to one that is live.
The brand kit panel beside the page: five surfaces named base, brand, muted, inverse, and brandStrong, each showing body text, muted text, a link, and primary and secondary buttons in the brand's colors, under the line Every pairing passes AA.

Your brand, set once, refused when it fails

The brand kit holds the colors, type, and spacing every page uses. Each pairing an author could produce is checked against AA as you type: text on every surface, links, buttons, banners, and type over photographs on both extremes of a scrim.

  • Change a color and every page follows on its next publish.
  • Versions of the kit are kept, like versions of pages.
  • What you see in the builder is the compiled page, not a preview of one.

Pages a marketer laid out, on a portal a developer built

The template pages that ship with Longeron, rendered exactly as an anonymous visitor sees them on Service Portal.

A broadband provider's campaign page: a hero over a suburban street at dusk, a banner naming the first neighborhoods, and three cards about installation day.
Campaign: Meridian Fiber
A university open day page: a hero over a campus quadrangle, a banner about registering, and three cards for talks, halls, and the library.
Campaign: Northgate Open Day
A campaign page for a free transit day: a dark hero with the date, then how it works in three cards.
Campaign: Ride Free Day
A service page for reporting a streetlight fault: a hero with one action, then what happens next.
Service: report a fault
A terms page: a short hero, then the conditions as headed sections.
Terms for a campaign
A utility company page that uses every section type: hero, banner, cards, price grid, terms.
Every component

Why it holds

Every one of these is a decision in the architecture, not a setting.

Your pages keep working when we are down.Compilation happens at publish time. Your instance serves finished output and never calls Longeron when a visitor opens a page.
Every version is kept.Publishing creates a version and never overwrites one. Compare any two; restore any one.
Nothing is edited behind your back.If someone changes a page in the instance by hand, the next publish stops and tells you what changed.
Links point at pages, not addresses.Rename a page and every link to it follows; the old address redirects.
Accessibility is enforced, not encouraged.WCAG 2.1 AA checks run on the compiled page, the same page visitors get.
Review where the page is.Comments pinned to a section of a version, with mentions by email, and a record of who published what.

Plans

Per workspace. Every plan has every feature: the builder, the gate, versions, review, and publishing to as many instances as you connect. Plans differ in how much you publish and how many people publish it. Pay annually and get two months free.

Trial

Free for 30 days

then choose a plan

Try it on your own instance. No card.

  • 10 pages
  • 200 MB of images
  • 3 people
Start a trial
Most popular

Team

$199 a month

or $1,990 a year

One marketing or communications team and one portal.

  • 200 pages
  • 5 GB of images
  • 25 people
  • Email support, next business day
Choose Team

Business

$599 a month

or $5,990 a year

Several teams, several portals, one workspace.

  • 2,000 pages
  • 50 GB of images
  • 250 people
  • Priority support, same business day
Choose Business

Enterprise

Custom

annual, invoiced

Procurement, security review, and invoicing on your paper.

  • Limits set with you
  • Annual invoicing
  • Security questionnaire and DPA
  • A named contact
Talk to us
What counts as a page?
A page in the builder, live or draft. Retired pages do not count.
Can we change plans?
Any time. Upgrades apply at once; downgrades at the end of the billing period.
Is there a per-instance charge?
No. Connect development, test, and production instances on any plan.
How do we pay?
Card, monthly or annually, through Stripe. Enterprise is invoiced.

Who it is for

Communications and marketing teams inside organizations that run a customer or employee portal on ServiceNow, and the platform owners who would rather not build landing pages by hand in AngularJS.

What it is not

Not a ServiceNow application: authoring, versions, and checks live in Longeron; a small renderer lives in your instance. Not an intranet builder. Not a form builder, in this version.

Does it need a developer to install?
An admin installs a small scoped app once and authorizes Longeron. After that, no.
What happens to our pages if we stop paying?
They keep serving from your instance as last published. You lose the editor, not the pages.
Where is our content stored?
In Longeron's database and image store, and in your instance once published. We hold no passwords for your instance; the connection is OAuth with a refresh token we seal.
Can we review pages before they go live?
Yes: comments pinned to a section of a version, with mentions by email.

Show us a page you wish marketing could ship.

We are talking to the first teams now. Bring a portal and a page; we will show you it live, published, and checked.

Talk to us Sign in