Skip to content

FAQ

Neubird is NeuBird’s Agentic SRE platform. It uses AI to automatically investigate production incidents, perform root cause analysis, and recommend remediation — acting as an AI teammate for engineering teams.

Neubird connects to your cloud providers, monitoring tools, and incident management platforms via read-only integrations. It queries your telemetry data in real-time using temporary credentials with minimal scope. See Security & Trust for details.

No. Neubird is fully ephemeral — telemetry data is processed in memory and automatically purged when an investigation session ends. There is no data lake, no archive, no historical data store.

No. Only metadata (field names, schemas, timestamps) is used in LLM prompts. Your actual telemetry data is processed in isolated, ephemeral environments. The LLMs serve as reasoning guides — they generate investigation plans and data retrieval programs, but never process your raw data.

Neubird uses a multi-model architecture: fine-tuned Llama models for telemetry program generation, Claude for investigation reasoning, and privately hosted open-source models for final analysis. The specific models are selected based on the task to optimize for accuracy, speed, and data security.

Yes. Neubird is SOC2 Type II certified with audited security controls and processes.

  • Platform — if you’re setting up Neubird for a team, managing connections, or want a web-based investigation environment
  • Desktop CLI — if you need direct database investigation or terminal-based workflows
  • MCP Server — if you use Claude Code, Cursor, or GitHub Copilot and want investigations in your editor

See Choosing an Interface for a detailed comparison.

Neubird supports 30+ integrations including:

  • Cloud providers: AWS, Azure, GCP, IBM Cloud, VMware, Snowflake
  • Monitoring: Datadog, New Relic, Prometheus, Grafana, Dynatrace, Elasticsearch, Sentry, Sysdig, SignalFx, OpenSearch, KloudFuse
  • Logging: Splunk, IBM Cloud Logs
  • Incident management: PagerDuty, ServiceNow, Slack, Atlassian Jira, incident.io, FireHydrant
  • DevOps: GitHub, GitLab, Azure DevOps
  • Databases: MongoDB, Redis, InfluxDB

See Connections overview for setup guides.

Initial setup takes about 5 minutes — create an account, set up a connection to your infrastructure, create a project, and start investigating. See the Platform Quick Start for a walkthrough.

Neubird uses pay-per-use pricing based on investigation hours. When Neubird isn’t investigating, there’s no charge. Contact NeuBird for pricing details.

Neubird follows a 7-step investigation process: hypothesis formation, dynamic investigation planning, telemetry program generation, secure data processing, real-time data access, iterative refinement, and final root cause analysis. See How It Works for the full architecture.

Yes. All investigation sessions are saved and accessible from the Platform dashboard. You can revisit past sessions to review queries, findings, and root cause analyses.

No. You can continue querying during an active session until your investigation is complete. Sessions remain active as long as needed.

No. Neubird uses strictly read-only access across all connections. This is architecturally enforced — it is technically impossible for Neubird to modify your systems or data.