# Shoreline

> Shoreline Software Inc. built an incident-automation / auto-remediation platform for cloud
> operations. It was acquired by NVIDIA in July 2024. As of 2026-08-29 the independent product
> surface is gone: shoreline.io and docs.shoreline.io have no DNS record, and www.shoreline.io
> returns HTTP 301 to https://www.nvidia.com/en-us/ for every path. There is no reachable
> Shoreline API, no OpenAPI, no MCP server and no A2A agent card. Do not attempt to integrate.

This file is GENERATED by the API Evangelist enrichment pipeline from the artifacts in this
repository, because Shoreline serves no llms.txt of its own (https://www.shoreline.io/llms.txt
returns 301). Generated 2026-08-29, method: generated.

## Status

- Company status: absorbed into NVIDIA (acquisition reported at ~$100M, July 2024)
- Website: https://www.shoreline.io/ — HTTP 301 to https://www.nvidia.com/en-us/
- Documentation: docs.shoreline.io — no DNS record (decommissioned)
- API: customer-cluster-specific endpoint; no public host, none reachable
- Machine-readable contract: none published (no OpenAPI / AsyncAPI / GraphQL / WSDL / protobuf)

## What still exists

- Terraform provider (unmaintained, last release 1.15.38 on 2025-04-22):
  https://registry.terraform.io/providers/shorelinesoftware/shoreline
- Provider source, archived and read-only, Apache-2.0:
  https://github.com/NVIDIA/terraform-provider-shoreline
- Provider documentation (the only surviving first-party developer docs):
  https://registry.terraform.io/providers/shorelinesoftware/shoreline/latest/docs
- Company page, retitled "Shoreline.io (Acquired by NVIDIA)":
  https://www.linkedin.com/company/shoreline-software

## What the platform modeled

Fifteen managed object types, derived from the Terraform provider schema: action, alarm, bot,
runbook, notebook, resource, file, integration, nvault_secret, smtp_subscription, principal,
time_trigger, dashboard, report_template, system_settings. The core loop is alarm (detect) ->
action (remediate) -> bot (bind the two).

## Authentication (historical)

Bearer token, customer/user-specific, supplied to tooling via the SHORELINE_TOKEN environment
variable, against a customer-specific cluster API endpoint. No OAuth, no OpenID Connect, no
public API keys.

## Artifacts in this profile

- packages/shoreline-packages.yml — the single first-party package and its release currency
- lifecycle/shoreline-lifecycle.yml — the end-of-life timeline
- authentication/shoreline-authentication.yml — the documented auth model
- data-model/shoreline-data-model.yml — the entity graph and its verbatim source schema
- well-known/shoreline-well-known.yml — the /.well-known/ probe (nothing served)
- security/shoreline-domain-security.yml — DNS/TLS/email posture of shoreline.io