New Sciple is live. Connect your AWS in 10 minutes and explore the platform with a sandbox workspace. Book a demo
sciple

Integrations catalogue

One platform.
Every tool your team already operates.

Sciple plugs into AWS, your source control, your identity provider, your messaging tools, and your Kubernetes clusters. Connect them once and they show up across every feature in the platform.

75+

Integrations in the catalogue

Across 13 categories: AWS, container orchestration, secrets, source control, identity, observability, security, and notifications. Connect once, surface everywhere.

  1. 6 AWS compute § 01
  2. 5 AWS networking § 02
  3. 11 AWS data § 03
  4. 3 AWS identity § 04
  5. 4 AWS dev tools § 05
  6. 3 AWS observability § 06
  7. 8 OSS observability § 07
  8. 12 Container orchestration § 08
  9. 6 Source control § 09
  10. 6 Identity / SSO § 10
  11. 4 Security scanning § 11
  12. 3 AI & MCP § 12
  13. 4 Workflow / notify § 13

  1. Stop 01 / 13 · AWS compute

    Discover, browse, and search every workload running in your AWS accounts.

    • EC2

      Instances, AMIs, autoscaling groups, load balancers, launch templates, and security groups.

    • ECS

      Clusters, services, task definitions, and live tasks across your AWS regions.

    • EKS

      Clusters, node groups, addons, and Fargate profiles discovered automatically.

    • Lambda

      Functions, layers, and event source mappings in one searchable view.

    • Step Functions

      State machines, executions, and the activities they invoke.

    • Auto Scaling

      Groups, policies, and lifecycle hooks alongside the instances they manage.

  2. Stop 02 / 13 · AWS networking

    See your VPCs, routing, edge, and DNS without dropping into the AWS console.

    • VPC

      VPCs, subnets, route tables, internet and NAT gateways, peerings, and endpoints.

    • Security groups

      Inbound and outbound rules, with anomaly detection for public ingress on sensitive ports.

    • CloudFront

      Distributions, functions, cache policies, and origin access controls.

    • Route 53

      Hosted zones, records, and health checks across every domain you manage.

    • Elastic IPs

      Allocated, associated, and idle addresses you may be paying for unnecessarily.

  3. Stop 03 / 13 · AWS data & storage

    Track every database, cache, storage volume, and backup in one place.

    • RDS

      Instances, clusters, snapshots, and subnet groups across your fleet.

    • RDS backups

      Automated and manual snapshot history per instance, with failed or missing snapshots flagged against the owning service.

    • ElastiCache

      Clusters, replication groups, and subnet groups for Redis and Memcached.

    • S3

      Buckets with object counts and policy posture across your accounts.

    • S3 replication

      Cross-region and cross-account replication rules with current sync state and lag per bucket.

    • EFS

      File systems, mount targets, and access points.

    • EBS

      Volumes and snapshots, including idle volumes worth removing.

    • EBS snapshots

      Snapshot lineage per volume with retention schedules and failed-snapshot alerts.

    • AWS Backup

      Backup vault contents, plan execution history, restore tests, and per-resource recovery point objectives. Failed and missed jobs route to the owning service.

    • Athena

      Workgroups, named queries, and recent query history alongside the S3 datasets they read from.

    • OpenSearch (AWS)

      AWS-managed OpenSearch domains, indices, and access policies surfaced in the same catalogue.

  4. Stop 04 / 13 · AWS identity & secrets

    Surface IAM, manage AWS-native secrets, and find permission drift fast.

    • IAM

      Users, groups, roles, policies, and instance profiles in one read-only view.

    • Secrets Manager

      Sciple’s credentials and secret configuration are backed by your AWS Secrets Manager. Create, read, update, and delete from the dashboard.

    • Parameter Store

      Hierarchical configuration backing for AWS-managed config values.

  5. Stop 05 / 13 · AWS developer tools

    Pipelines run on the AWS tools you already pay for and operate.

    • CodePipeline

      Pipelines provisioned and tracked from Sciple, owned per service and environment.

    • CodeBuild

      Build projects backed by AWS managed runners, no extra infrastructure to operate.

    • CodeDeploy

      Deployment groups and rolling strategies wired up automatically.

    • ECR

      Container registries with image inventories and unused repository detection.

  6. Stop 06 / 13 · AWS observability

    See native AWS telemetry in context, without copying logs out of your account.

    • CloudWatch

      Logs, metrics, and alarms surfaced alongside the resources they describe.

    • X-Ray

      Distributed traces linked from the services that produced them.

    • CloudTrail

      AWS-side audit history alongside Sciple’s own action log.

  7. Stop 07 / 13 · Open-source observability

    Wire your existing metrics, logs, and tracing stacks into the service catalog and into the unified per-service dashboard that overlays all three pillars.

    • Unified dashboard

      A single per-service canvas that overlays logs, metrics, and traces side-by-side, drawing from any combination of the sources below. No tab-switching during incident triage.

    • Prometheus

      Scrape endpoints and recording rules surfaced per service. Metrics overlay onto the unified dashboard alongside logs and traces. Alerts route through Sciple.

    • Grafana

      Service-aware Grafana dashboards linked directly from each service, with panels embeddable into the Sciple unified view.

    • Loki

      Grafana-stack log aggregation. Service-scoped log streams render in the unified dashboard next to metrics and traces.

    • Jaeger

      OpenTracing-compatible distributed traces stitched to the services that produced them, with spans overlayable on the unified dashboard timeline.

    • OpenTelemetry

      Vendor-neutral metrics, logs, and traces via OTLP ingestion. A single OTel pipeline feeds the unified dashboard for all three pillars.

    • Elasticsearch

      Elastic Cloud and self-hosted clusters as a log-search backend, queryable from the unified dashboard log panel.

    • OpenSearch

      Self-hosted OpenSearch clusters as a log-search backend, with index and policy visibility.

  8. Stop 08 / 13 · Container orchestration

    First-class support for both Kubernetes (EKS) and ECS, with live resource browsing and a shared job execution surface tied to the service catalog.

    • ECS clusters

      Clusters, services, and live tasks discovered from the cloud module across every region, scoped to the owning service.

    • ECS services

      Service definitions, rollout state, and active task counts, with deployment history per service-and-environment pair.

    • ECS task definitions

      Task definition revisions and the services that reference them, with image, CPU, and memory diffs across versions.

    • Fargate

      Serverless container runtime treated as a first-class compute target across both ECS and EKS.

    • Scheduled jobs (Fargate)

      Cron jobs defined in Sciple and executed as ECS Fargate tasks in your AWS account, scoped to the owning service.

    • Ad-hoc jobs (Fargate)

      One-shot tasks (migrations, backfills, data fixes) launched on demand as Fargate tasks, with logs and ownership in the catalog.

    • EKS clusters

      Kubernetes clusters auto-discovered from the cloud module, no kubeconfig copy-paste.

    • Kubernetes Jobs / CronJobs

      Run scheduled and ad-hoc work as native K8s Jobs and CronJobs on a connected EKS cluster instead of Fargate.

    • Live pod view

      Pods update as their state changes so you do not refresh the page.

    • Custom resources

      Browse and inspect any CRD installed on your clusters.

    • Helm charts

      Helm releases as a first-class resource alongside the rest.

    • Admission policies

      Mutating and validating webhook configurations, surfaced in one table.

  9. Stop 09 / 13 · Source control

    Native providers for the four source-control systems your team probably uses.

    • GitHub

      Cloud and Enterprise. Backed by a personal access token or a GitHub App.

    • GitHub App

      Install once for your organization. Repositories appear in Sciple automatically.

    • GitLab (SaaS)

      gitlab.com with personal or group access tokens.

    • GitLab (self-hosted)

      On-prem and self-managed instances with the same feature set.

    • Bitbucket

      Cloud and Data Center, with branch protection awareness.

    • Azure DevOps

      Per-organization or per-project, with repositories surfaced live.

  10. Stop 10 / 13 · Identity & single sign-on

    OIDC-based single sign-on, configurable per workspace.

    • Okta

      Wire up Okta in minutes with a standard OIDC application.

    • Entra ID

      Microsoft Entra ID (formerly Azure AD) with claims mapping.

    • Google Workspace

      Sign in with Google accounts in your organization.

    • Auth0

      Auth0 as your identity provider, configured with a standard OIDC application.

    • Any OIDC IdP

      Bring any OIDC-compliant identity provider, including PingFederate and Keycloak.

    • Local accounts

      Username and password fallback for emergency and break-glass access.

  11. Stop 11 / 13 · Security scanning

    Four scanning pillars feed one ASPM workflow.

    • Code (SAST)

      Static analysis, secret scanning, and dependency (SCA) scanning across every major language ecosystem.

    • DAST

      Dynamic testing of running applications for SQL injection, cross-site scripting, broken auth, and SSRF.

    • Infra / Server

      Container image scanning, EC2 and Lambda host scanning via AWS Inspector, IaC scanning, and Kubernetes manifest scanning.

    • Cloud

      AWS Security Hub, GuardDuty, IAM Access Analyzer, and other AWS-native findings aggregated into the ASPM queue.

  12. Stop 12 / 13 · AI & MCP

    Bring your AI assistant into the platform to author automation, with humans approving every change.

    • Claude (MCP server)

      A standalone Model Context Protocol server exposes runbook authoring as tools Claude can call. Claude drafts runbooks; engineers review and promote them in Sciple.

    • Claude Code

      Run the Sciple MCP server inside Claude Code to build and edit runbooks from your terminal, authenticated with a scoped access token.

    • Claude Desktop

      Connect the Sciple MCP server to Claude Desktop and author runbooks in a normal chat, then approve them in the Sciple UI.

  13. Stop 13 / 13 · Workflow & notifications

    Push platform events to where your team already pays attention.

    • Slack

      Pipeline statuses, finding alerts, and approval requests in your channels.

    • Microsoft Teams

      The same notifications, routed to Teams instead.

    • Email

      Per-user digest emails for findings approaching SLA breach.

    • Webhooks

      Signed JSON callbacks to any URL you operate.