Skip to content
SanShivaSHELL ELOS

Integrations

Orchestrates your stack. Replaces none of it.

Your identity provider, cloud, source control, tracker, documentation and on-call tools stay the systems of record. ELOS connects them and runs the workflows that fall between them.

Integrations by category

Each connection is checked when you add it. Nothing shows as connected until the system answers.

Verified
Connect and verify it yourself today.
Guided setup
Connector built; we set it up with you during onboarding.

Identity and SSO

Your engineer roster and groups, through the identity provider you already run.

  • Microsoft Entra ID

    Users and groups

    Verified
  • Google Workspace

    Users and groups

    Verified
  • Okta

    Users, groups and app assignments

    Guided setup

Source control

Repositories and who works on them, for ownership and day-one access.

  • GitLab

    Projects, groups and members

    Verified
  • GitHub

    Repositories, teams and members

    Guided setup
  • Bitbucket

    Repositories, projects and members

    Guided setup

Cloud

Cloud accounts and the time-bound access engineers need in them.

  • AWS

    Accounts and access

    Verified
  • Microsoft Azure

    Subscriptions and access

    Verified
  • Google Cloud

    Projects and access

    Verified

Work tracking

Projects and work items, linked to the people and services they belong to.

  • Jira

    Projects and work items

    Guided setup

Knowledge

The documents Ask ELOS answers from, with citations.

  • Confluence

    Spaces and pages

    Guided setup
  • Notion

    Pages and databases

    Guided setup

Incident and on-call

Services and on-call context, tied to ownership.

  • PagerDuty

    Services, schedules and incidents

    Guided setup

Communication

Onboarding and access notifications where your team already talks.

  • Slack

    Users and channels, for notifications

    Guided setup

Don't see your tool? Tell us what you run and we'll walk you through the options.

How connections are protected

  • Credentials in a secrets store

    Connector credentials are kept in a dedicated secrets store, never in the application database.

  • Least privilege

    Each connector asks only for the scopes it needs, and each connection is verified when it is added.

  • Your system stays in charge

    ELOS reads and drives workflows; your tools remain the source of truth and keep their own controls.

What ELOS is not

  • Not your HR system. It starts where HR hands over.
  • Not your service desk. It drafts the ticket and links it.
  • Not your identity provider. It works through yours.
  • Not another wiki. It makes the knowledge you already have answerable.

How credentials and data are protected in detail: Security and trust.