Discover running apps
Surface the apps already running on your hosts, like containers and listening services, into a review inbox.
Deliver
Service Discovery
Find what you already run, and bring it onto the paved road
You do not have to register every service by hand. IntegraCI discovers the applications already running on your hosts and detects the stack of any repository, then proposes a one-click onboard. A running app is imported as it is, with no re-provisioning, and a human reviews every promotion. A new repository gets a golden-path suggestion and a service created for it. Discovery itself is read-only.
- A service catalog that reflects what actually runs, not just what was registered by hand
- Every service onboard reviewed and recorded before it enters the paved road
- New repositories land on a consistent golden path from the first commit
The problem
You have services running in production that no one has ever registered, and repositories whose stack no one has cataloged. Onboarding each one by hand means engineers either skip it or spend time filling forms, so your service catalog drifts further from what actually runs in your environment.
Without IntegraCI
- Services running in production with no catalog entry
- Stack detection done by asking the owning team
- Silent onboards or no onboards at all
- No record of when or why a service was registered
With IntegraCI
- Running apps surface into a review inbox from your hosts
- Repository stack detected and a golden-path proposed
- Every promotion reviewed before anything is registered
- Each onboard recorded with the evidence behind it
What you get
Register-only import
Promote a discovered app to the catalog as it runs, with no re-provisioning of the live workload.
Repo stack detection
Point at a repository and IntegraCI detects its language and framework, then suggests a golden path.
Human in the loop
Every promotion is reviewed and approved in the inbox; nothing is onboarded silently by default.
Read-only and audited
Discovery only reads, and each onboard is recorded with the evidence behind it.
How it works
- 1
Discover
IntegraCI collects the apps running on your hosts and the stack of your repositories.
- 2
Review
Candidates land in an inbox with their evidence and a suggested onboarding.
- 3
Onboard
Approve to register a running app as it is, or scaffold a repository onto a golden path.
How it stays governed
The same gates everyone passes, applied here.
Gated by policy
Discovery runs as a read-only scan, and nothing is promoted to the catalog without a human approving the candidate in the review inbox. The golden-path suggestion for a repository is driven by policy as code, so every new service lands on the same baseline configuration rather than whatever the author happened to remember.
Recorded, tamper-evident
Each onboard writes once to a tamper-evident audit trail with the evidence collected during discovery, so you can show what was running, when it was detected, and who approved it.
A human in the loop
Every candidate discovered on a host or in a repository waits in the inbox for a reviewer to approve or dismiss it. Nothing is onboarded silently; a person is the gate before any service enters the catalog.
Works with your stack
Connect the tools you already run.
Source control connectors feed repository stack detection; infrastructure connectors surface running apps and listening services from your hosts.
- Atlassian
- Gerrit
- Gitea
- GitHub
- GitLab
- Microsoft
- Apple
- Argo Project
- AWS
- Cloudflare
- CNCF
- Coder
- Crunchy Data
- Daytona
- Env0
- Keycloak
- MongoDB
- +11 more
Who it’s for
Where teams reach for it.
Catalog an inherited fleet
When your team takes ownership of a set of running services with no catalog entries, IntegraCI surfaces them from your hosts into a review inbox. You approve each one as it runs, with no re-provisioning of the live workload.
Onboard a new repository to the golden path
Point IntegraCI at a new repository and it detects the language and framework, then proposes a golden-path scaffold. A reviewer approves before a service entry is created, so the team starts from a consistent baseline rather than blank config.
Bring shadow workloads onto the governed road
Workloads that were never registered appear in the discovery inbox, giving a compliance team visibility into what is running and a controlled, audited path to bring each one under governance before the next review cycle.
Questions, answered.
Does IntegraCI scan my hosts directly, or does it rely on my existing inventory tools?
IntegraCI reads from your connected infrastructure and source control connectors to surface running apps and repository stacks. Discovery is read-only and does not deploy agents or modify anything on your hosts.
Will onboarding a discovered service re-provision or restart it?
No. A discovered app is imported as it runs, registering it in the catalog without touching the live workload. Re-provisioning is a separate, opt-in action and is never triggered by discovery itself.
Can we control who reviews and approves discovered candidates?
Yes. The review inbox is governed by role-based access with database-enforced row-level security, so only authorized reviewers see and act on candidates within their scope.
What happens if we dismiss a candidate we later decide to onboard?
Dismissed candidates are preserved in the tamper-evident audit trail. You can re-trigger discovery or manually register a service at any time, and the prior dismissal remains part of the history.
Put Service Discovery on your stack.
Request a demo, or read the docs to see how it fits the tools you already run.