STRINGER Contact Sales

Getting started

Most Stringer customers reach production in 30 days. Here’s what that timeline looks like and what we need from you.

Day 0 — Kickoff

Once your contract is signed, we hold a kickoff call within five business days. On that call:

  • We confirm your deployment model (Managed Cloud / Dedicated Tenant / Federal) and target environment.
  • We exchange security and compliance contacts.
  • We collect your initial identity provider (IdP) details (Okta, Azure AD, Google Workspace, Ping, etc.).
  • We hand off a shared Slack channel and your dedicated TAM (Enterprise tier).

Days 1–10 — Environment provisioning

We provision your Stringer environment:

  • Tenant (single-tenant for Dedicated and Federal; logical isolation in Managed Cloud).
  • HSM-backed key material (dedicated HSMs for Dedicated and Federal).
  • Region selection, including data-residency constraints if required.
  • Initial admin accounts and break-glass procedures.

You don’t need to do anything here except be available for clarifying questions.

Days 5–15 — Identity federation and policy import

In parallel with provisioning:

  • We connect your IdP via OIDC or SAML, with SCIM provisioning for groups.
  • You hand us your existing access policy (or your closest approximation — we’ll help formalize it).
  • We translate it into Stringer’s ABAC policy language, side-by-side with your security team.
  • We dry-run the policy in audit mode against synthetic events.

Days 10–25 — Agent rollout

The Stringer agent is a single Rust binary on Linux, macOS, and Windows. Rollout options:

  • MDM-driven (Jamf, Intune, Kandji, Workspace ONE) — the fastest path. We supply a signed package and a configuration profile.
  • Self-service — for smaller fleets, users install via your internal package manager.
  • Bring-your-own-tooling — we’ll integrate with whatever you already use to push binaries.

We start with a pilot group (typically engineering or security), then expand in waves.

Days 25–30 — Cutover

  • We move policy enforcement from audit mode to deny mode for the pilot group.
  • We monitor for false positives jointly for one week.
  • Once the pilot is clean, we begin production rollout in waves matched to your change-management cadence.

What we need from you

  • An executive sponsor for the project.
  • A primary contact in security and one in IT/operations.
  • IdP admin access (for federation only — we don’t need ongoing access).
  • A list of resources you want protected, with owners.
  • Decision authority on policy edge cases (we provide the recommendation; you sign off).

What we deliver at go-live

  • Production Stringer environment, monitored 24/7.
  • Documented policy in version control.
  • Audit evidence package mapped to your compliance frameworks.
  • Runbooks tailored to your environment.
  • A 30-day post-go-live tuning window.