Skip to content

Engineering Practice

How Endeavor Engineering builds, tests, releases, and supports software.

We publish this because it is a fair question from anyone evaluating a small engineering organization: how do you know your releases are sound, and what happens when something breaks? These pages are the answer, in the same form our own engineers use.

Available here

  • What You Can Rely On in an EEI Seeq Connector

    A connector built into Seeq is kept current by Seeq's own pipeline. What an EEI connector gives you in its place, concern by concern, with the evidence and what is not in place yet.

  • Getting Support from EEI

    How to reach us, what we commit to — a response within one business day — and how specific service levels get agreed before an engagement starts.

  • How We Build, Release and Deliver

    The path from a code change to your environment: the CI we run today, the managed delivery we perform today, and the continuous delivery we are building on top of it.

  • Validating Seeq Integrations Against Seeq Continuous Delivery

    Seeq validates its own connectors with every release; third-party integrations get no such guarantee by default. How we close that gap — and how it works for our Seeq connectors.

  • Reading an EEI Version Number

    What the digits do and do not claim, and why a connector's version starts with a Seeq SDK line rather than a Seeq server version.

What lives elsewhere

Internal engineering standards, runbooks, and platform design records are maintained privately.

Some of what you might expect here is deliberately on the page that owns it rather than duplicated:

  • How we evidence a release — test tiers, and what we can actually produce for a review — is part of our compliance posture.
  • Per-product compatibility and release notes live with each product, because the validated platform version is specific to it. This section covers how to read those numbers, not what they are.
  • The connector support commitment in full — including where our boundary sits — is on Connectors ++, stated once and referenced by every connector rather than restated per product.

Pages appear here as they are written.

If something you need is missing, asking is the fastest way to get it written.

Ask us about a topic →