# GatewayLabs

> GatewayLabs is one operational product with two connected workflows: Release Check before deployment and Incident Answer during an incident. ConfigDiff and Signal remain technical compatibility names. Specfold is a separate local-first desktop companion.

Choose the GatewayLabs workflow by task:

- Incident Answer (Signal module): post-release incident clarity for application failures, API gateway errors, Elastic/OpenSearch pressure, Windows/Linux resource signals, recent deploys, infrastructure changes, and safe incident reports.
- Release Check (ConfigDiff engine): pre-release configuration drift comparison for appsettings, web.config, environment variables, CI/CD release gates, scheduled drift checks, and change evidence that can be linked to an incident.
- Specfold by GatewayLabs: lightweight local-first desktop companion for cleaning messy OpenAPI, Swagger, Postman, Insomnia, HAR, HTTP, and cURL inputs into editable collections with scoped base URLs and folder tokens, resizable request/response panels, safe multipart uploads, and portable exports.

Incident Answer does not call an external AI/LLM provider. Its current customer result is deterministic; future model assistance is limited to GatewayLabs-trained artifacts that pass the documented data, evaluation, parity, and pilot gates.

## Primary Pages

- [GatewayLabs home](https://gatewaylabs.net/): overview of Release Check and Incident Answer.
- [Specfold](https://gatewaylabs.net/specfold): local-first desktop companion for turning messy OpenAPI, Postman, Insomnia, HAR, HTTP, and cURL inputs into clean, independently collapsible API collections with scoped gateway routing, effective URL context, safe form-data file upload testing, and copyable exports.
- [Incident Answer](https://gatewaylabs.net/signal): incident workflow page and optional fixed-scope review offer.
- [Studio user guide](https://gatewaylabs.net/docs/studio): task-first authenticated guide for choosing Release Check or Incident Answer; workspace access; roles and plan requirements; first workflows; automations; billing; and security boundaries. Specfold remains separate.
- [Pricing](https://gatewaylabs.net/pricing): one GatewayLabs software offer plus the optional fixed-scope incident review.
- [Demo](https://gatewaylabs.net/demo): demo workspace with production-like incident and config drift data.
- [Incident Answer docs](https://gatewaylabs.net/docs/signal): Signal-module setup, sources, agent model, and security docs.
- [Release Check docs](https://gatewaylabs.net/docs/configdiff): ConfigDiff-engine comparison, results, projects, alerts, and rollout.
- [Specfold docs](https://gatewaylabs.net/docs/specfold): spec cleanup, first request, import/export, scoped base URLs, and local-data security.
- [Task chooser](https://gatewaylabs.net/docs): choose the shortest guide without knowing product names.

## Recommended Technical Guides

- [GatewayLabs Blog](https://gatewaylabs.net/blog): practical notes on incident clarity, offline evidence packs, Azure DevOps timelines, and config drift prevention.
- [Restricted-network incident pilot readiness checklist](https://gatewaylabs.net/blog/restricted-network-incident-pilot-readiness): First Incident Wizard, hosted, hybrid, and offline pilot checklist for safe incident clarity validation before production data is shared.
- [What the first 15 minutes of an incident should produce](https://gatewaylabs.net/blog/first-15-minutes-incident-clarity): source ranking, first query, recent changes, and handoff checklist.
- [Offline incident evidence packs for restricted networks](https://gatewaylabs.net/blog/offline-incident-evidence-pack): safe local evidence collection without raw log export.
- [Azure DevOps deploy regression timeline](https://gatewaylabs.net/blog/azure-devops-deploy-regression-timeline): correlate deploys, config, Terraform, Kubernetes, and runtime symptoms.
- [Config drift before release checklist](https://gatewaylabs.net/blog/config-drift-before-release-checklist): known-good baselines, policy-aware comparison, and release decisions.
- [API gateway 503 runbook template](https://gatewaylabs.net/blog/api-gateway-503-runbook-template): first-responder template for route, upstream, query, change, and handoff context.
- [Nexus package pull build failure](https://gatewaylabs.net/blog/nexus-package-pull-build-failure): pipeline/package restore failure taxonomy for Nexus, proxy, registry, and dependency pull incidents.
- [Private-network Signal agent checklist](https://gatewaylabs.net/blog/private-network-signal-agent-checklist): restricted-network rollout checklist for scoped tokens, local alerts, and offline evidence.
- [Azure DevOps config drift release gate](https://gatewaylabs.net/blog/azure-devops-config-drift-release-gate): release gate workflow for .NET, IIS, ConfigDiff, and Azure DevOps.
- [API gateway 503 and timeout triage](https://gatewaylabs.net/guides/api-gateway-503-timeout-triage): gateway 503, upstream timeout, route, deploy, and config correlation workflow.
- [Signal for API gateway incident clarity](https://gatewaylabs.net/signal/api-gateway-incident-clarity): how Signal connects gateway errors, upstream service logs, recent deploys, and config drift.
- [Azure DevOps deployment incident timeline](https://gatewaylabs.net/guides/azure-devops-deployment-incident-timeline): join deploys, commits, work items, config drift, Terraform, Kubernetes, and runtime failures.
- [Elasticsearch and OpenSearch incident triage](https://gatewaylabs.net/guides/elasticsearch-opensearch-incident-triage): cluster health, shard pressure, disk pressure, dependency latency, and app-facing timeouts.
- [Kubernetes rollout 503 debugging](https://gatewaylabs.net/guides/kubernetes-rollout-503-debugging): ingress, service endpoints, readiness, rollout history, config maps, secrets, and application errors.
- [Config drift monitoring for Azure DevOps](https://gatewaylabs.net/guides/config-drift-monitoring-azure-devops): known-good baselines, policy rules, CI/CD gates, and scheduled config checks.
- [Incident Clarity Sprint](https://gatewaylabs.net/guides/incident-clarity-pilot): one-time fixed-scope professional service for one incident, one report, one readout, and one correction round.
- [ConfigDiff vs manual config review](https://gatewaylabs.net/compare/configdiff-vs-manual-config-review): when automated config drift checks are better than manual release review.

## Contact

- Email: orkun@gatewaylabs.net