About

We’re a small
software company.

Brevard Creek Labs builds and operates software products from the mountains of North Carolina.

Layered ridgelines receding into haze, with a creek running along their foot.
Fig. 1 — The ridgelines above the creek, built from the vertices that matter — summit, saddle, summit — rather than from a smoothed curve, because smoothing removes the one thing a summit is.

01

What we do

We work on a small number of products at a time and try to make each one genuinely useful.

We write the software, run the systems behind it, and support the people who use it. The same people do all three, which is why a bug report and the fix for it do not have far to travel.

We use our own products every day — our documents, our mail, our workflows — so the annoying parts get fixed because we are the ones being annoyed by them.

What we build is the short list: two products you can use today and one in development.

02

Small by design.

We’re a small team, which means the people building the software are close to the people using it.

There are no layers of product committees between an idea and the person who writes the code.

03

Why Brevard Creek?

The company is named after Brevard Creek, a real creek in western North Carolina.

04

How it is run

How Brevard Creek Labs is built and operated
WhoA small team in western North Carolina. Everybody here builds.
Where it runsOur own servers, administered by us, rather than rented as a managed service with our name on it.
What we depend onTwo companies: one hosts the servers, one carries outbound email. Both are named on the privacy page.
CallsBrowser to browser wherever the network allows it. The audio and video do not pass through us.
CookiesTwo, once you sign in: the session itself, and a hint that carries nothing and lets a page know you are signed in before it has to ask. The chat widget on these public pages keeps its own conversation in your browser’s local storage.
MeasurementNo analytics scripts, no advertising tags, no third-party trackers, and no cookie on the public pages. The web server keeps a standard access log. The one other thing we keep is a vote: when you press “I have this problem too” we store a salted, one-way hash of your address so the same person cannot vote twice. It cannot be reversed and it is not joined to anything.
BackupsDaily. Fourteen days of restore points, checked automatically.
AccountsMade by an administrator. There is no self-serve sign-up.
RevenueWe are early, and we would rather say that than print a number we made up.

We also run an internal workspace called the Virtual HQ, where we test the parts of our software that are not products yet.

Have a question about any of this? Write to us.