Skip to main content

​
Overview

nOps supports two kinds of integrations:
  • Cloud providers — AWS, GCP, and Azure accounts for billing data, recommendations, and commitment management.
  • Third-party apps — developer and SaaS tools (such as Cursor) for usage and billing visibility.
Cloud and third-party integrations are managed from Settings in the nOps dashboard (/settings).

​
Cloud provider integrations

Once connected, nOps pulls billing and usage data from your cloud accounts into the platform, enabling cost visibility on your canvases and powering commitment management features. Commitment Inventory (Optimize → Commitments → Inventory) is available on every plan for members, admins, and owners when the relevant cloud integration is active. Scheduled inventory emails require Inform. nOps supports three cloud providers:

AWS

Onboard your payer account for savings analysis—we’ll guide you through linking billing data securely so nOps can analyze spend and recommendations.

Google Cloud

Connect via a service account with BigQuery access to your billing export datasets.

Microsoft Azure

Connect via admin consent and a service principal with RBAC roles for cost management and FOCUS exports.
Use Settings → Cloud Onboarding to add a new cloud account. Connected accounts appear under Settings → Account Status → Cloud accounts. Permissions: Only Admin and Owner users in your nOps organization can add, remove, or manage cloud integrations (including connecting AWS and using Manage on an existing integration). Members cannot. See Users and roles.

​
Third-party integrations

Connect developer tools and SaaS products from Settings → Integrations (/settings/integrations, or View all from the Settings preview). Connected apps also appear under Settings → Account Status → Connected apps. Permissions: Only admins and owners can connect, re-validate, or disconnect third-party apps. Members can view status but see Admin Only on connectable integrations.

​
Cost integrations (Inform)

These integrations bring third-party spend into Inform for unified cost visibility, attribution, and optimization.

Datadog

Retrieve and analyze Datadog cost data for unified expense visibility and resource allocation optimization.

MongoDB Atlas

Monitor MongoDB Atlas expenses across projects with organization API keys and centralized cost management.

Fastly

Bring Fastly CDN cost and usage into Inform for attribution and optimization.

OpenAI

Track OpenAI API usage costs with detailed model usage and spending patterns.

Anthropic (Platform)

Analyze Claude Platform (Console) API usage and billing in Inform with real-time cost insights.

Claude.ai (Enterprise)

Claude Enterprise (claude.ai) usage in Inform and per-user AI seat tracking in Budgets (with read:members and read:spend_limits; optional write:spend_limits for limit edits).

Twilio

Monitor Twilio communication costs with visibility across products and usage categories.

Amazon Bedrock

Track Bedrock AI model usage and costs through Model Invocation Logs. Connect one or more S3 buckets or prefixes for comprehensive AI spend visibility.

Snowflake

Bring Snowflake warehouse credit consumption, query history, and organization-level spend into Inform using key-pair authentication.

Vercel

Connect Vercel platform billing and AI Gateway usage for unified cost visibility.

​
Developer and management tools

Cursor

Connect your Cursor team with a Team Admin API key for usage visibility and AI seat tracking in Budgets.

Atlassian

Track Atlassian usage and user activity to identify idle users and optimize license allocation.

GitHub

Connect a GitHub personal access token to bring organization or enterprise billing, usage, and seat data into Inform.

GitLab

Connect a GitLab.com access token to bring subscription, seat, and usage-quota data into Inform.

​
Issue trackers (Notifications)

Connect Jira and Linear from Settings → Integrations → Notifications (/settings/integrations?tab=notifications) to create issues from nOps recommendations. OAuth is used for both providers; credentials are stored securely and are not entered as API keys in the integrations form. Email, Slack, and Teams notification delivery are configured separately under Settings → Notifications (/settings/notifications). For Slack notifications, SSO, and other platform integrations outside this catalog, see the nOps integrations overview on the help site.

​
AWS onboarding

Follow these guides to connect your AWS payer account for cost and usage visibility.

Integration setup

Savings analysis onboarding: connect billing export and a secure cross-account role in a few steps.

Commitment management

Optional second step after AWS integration: CloudFormation + StackSets roles, then in-product verification.

​
Google Cloud Platform onboarding

Follow these guides to connect your GCP billing data and enable commitment management.

Prerequisites

Set up billing exports and prepare your GCP environment for nOps.

Integration setup

Link your GCP billing data to nOps, configure Domain Restricted Sharing when required, and grant service account permissions.

Commitment management

Configure nOps to manage GCP Committed Use Discounts (CUDs) on your behalf.

​
Microsoft Azure onboarding

Follow these guides to connect your Azure environment and enable cost visibility.

Prerequisites

Understand billing account types, locate your Management Group ID, and prepare your Azure environment for nOps.

Integration setup

Connect your Azure environment to nOps and assign the required RBAC roles for cost visibility.

Next: Users and roles

Learn how to invite team members, assign roles, and manage permissions.