Skip to main content
All work
Status: Built At Oracom Intelligence

Secure delivery pipeline for on-site AI assistants

A major refactor of how on-site assistant devices are taken in, registered, connected over an encrypted channel, and started remotely.

  • TypeScript
  • Node.js
  1. Step 1: Intake
  2. Step 2: Registration
  3. Step 3: Encrypted connection
  4. Step 4: Remote start
The four stages every on-site device goes through. Conceptual, no internals.

Context

Some of the platform's AI assistants run on physical devices at customer sites. Before a customer can use one, the device has to be taken in, registered, connected securely, and started, without someone standing next to it.

My role

I carried out a major refactor of this delivery and usage pipeline.

What I built and decided

  • One pipeline covering intake, registration, encrypted connection, and remote start.
  • Remote start, so a device can be brought up without on-site work.

Outcome

Intake, registration, encrypted connection, and remote start now run as one refactored pipeline.

What I'd do next

Move device onboarding onto the continuous-delivery path from the infrastructure rebuild, so pipeline changes ship the same way as the rest of the platform.