Skip to content

About

Auxon is a senior IT operations and AI enablement practice.

Founder

Oleg Strutsovski

Ex-Life360, where he built Okta to over 300 integrations, ran IT for a roughly 900-person remote-first org including hardware teams, and owned SOX IT general controls. Builds production AI tooling for IT operations.

Ex-Life360300+ Okta integrationsSOX ITGC550-device MDM
300+ Okta integrations900-person public co550-device MDM fleetSOX ITGC

Principles

Three principles

01

Build, then advise.

We ship the system before we draft the doc. The runbook reflects the production we are running.

02

Defaults that survive an audit.

Identity, devices, compliance: configured for an auditor first. Drift gets caught, not papered over.

03

AI where it removes manual work.

We use AI to retire toil, not to demo on a deck. Every prompt has a measurable outcome.

Most consultancies advise. We operate.

Operating means we carry pagers, not just decks. When we design your identity or device systems, we have already shipped that exact configuration under audit pressure and kept it running without a team of five dedicated engineers.

What operating, not advising, means

We scope engagements around outcomes: a working Okta build, a passing audit, a fleet that enrolls itself. Deliverables are production-ready systems, not recommendations. We stay until it is live and documented.

Background

Why Auxon

Most IT work in our industry runs as an outsourced advisory: a deck, a recommendation, a handoff. The result is a beautiful plan and a stuck operator.

Auxon was built to flip that. We run the systems we sell. Our products, Paragon, Trueform, and NetMender, come from the same operator playbook our consultancy uses. Every guardrail in them was written because we hit the gap ourselves.

The team has run identity for fast-scaling public and private companies, owned SOX ITGC, shipped 550-device MDM migrations, and built Okta to 300+ integrations. Everything here is built from that practice.

How we work

Three ways to work with us.

We want you to be clear on the shape of the engagement before you commit. We do scoped projects, ongoing retainers, and early access to our products. Most teams fall into one; some start with a project and move to a retainer.

01

Scoped project

You know what you need and want a fixed scope with a clear end. Okta builds, MDM migrations, SOC 2 prep, AI rollouts. Typical engagement is 6 to 12 weeks with defined deliverables agreed up front.

Who it is for

  • Founders and IT leads who can name the deliverable.
  • Teams with a deadline or an audit driving urgency.
  • Orgs that need outside hands for one well-defined job.

How to start

02

Ongoing retainer

A senior operator embedded part-time and on-call. Identity, devices, and compliance maintained as part of normal operations: incidents handled, new systems onboarded, controls kept current.

Who it is for

  • 50 to 1,000 person orgs that have outgrown solo IT.
  • Teams without a dedicated IT or security hire.
  • Orgs that want a consistent operator, not a new ticket queue.

How to start

03

Product early access

Run Paragon, Trueform, or NetMender on your own stack. Invite-only while we are in early access. You get the product, direct access to the team, and influence over what gets built next.

Who it is for

  • Operators running Okta or a multi-tenant identity stack.
  • Teams managing MDM at scale.
  • Anyone running a multi-vendor LAN (Meraki, UniFi).

How to start

Connect

Want to work together?

Book a call