What nventr connects to, by mechanism. Everything marked today is in the product now; anything else says so.
The managed host is included. The same stack runs in your account or on one VM, and the license moves with it.
The managed fleet and the self-host target: ECS Fargate, S3, SSM and Secrets Manager, CloudFront, CodeCommit, SES. Any other AWS API is a SigV4 integration.
Firebase Auth, Firestore and Hosting are one of the two data planes; the plane itself runs on it.
Postgres, GoTrue auth and storage as the second data plane; the default on a self-host stamp.
S3-compatible object storage for self-host and air-gapped stamps, behind the same S3 endpoint seam.
Docker Compose behind Caddy, split into a data tier and a blue/green app tier; a kit release lands as a swap.
A second place to run: App Kit instances on native Azure (Container Apps, Blob Storage, Key Vault, Container Registry, Log Analytics, Azure Database for PostgreSQL, Communication Services Email) or as sealed images on a VM in your subscription; hosted instances on Azure VMs from the plane. One switch, CLOUD_PROVIDER=azure, selects every driver.
Sign in with the directory you already run; provision from it.
Per-organization single sign-on from Platform Business; “Continue with SSO” discovers the provider from the email domain, and SSO can be enforced for verified domains.
Any SAML or OIDC identity provider; these are the ones the console names in its setup steps.
Users and Groups endpoints per organization with a bearer token, creating members and access grants from your directory. Enterprise.
A hosted App Kit instance trusts the platform: one login, the same organization role on every instance.
Where the documents agents answer from come in. New material arrives as a draft; a person publishes it.
Sites and document libraries, synced hourly, daily or weekly.
Spaces and pages on the same schedule.
Folders you share with the connector.
A folder, recursively, through a scoped app — PDF, Word, text and Markdown.
Pages and databases under a shared integration.
A bucket or prefix, in your account or ours.
Your public site, crawled on the schedule you set.
PDF, Word, text, Markdown and CSV uploaded directly, including thousands at a time through a Dev Console session.
Not connectors today. Upload the files, point a crawl at a shared site, or tell us which one you need first.
A side effect is a capability you declare on the pipeline. Undeclared means the call does not happen.
Declared once with its base URL and actions. Auth: none, bearer, API key, OAuth 2.0 client credentials, or AWS SigV4. NetSuite, Salesforce, HubSpot, Zendesk, Jira, QuickBooks and the rest are reached this way — there is no vendor SDK between you and the call.
Signed POSTs to a URL you own, with delivery status on every event.
Incoming webhooks as notification integrations: gate held, run failed, invoice posted.
Any SMTP relay — Microsoft 365, Google Workspace, Amazon SES, or the mail server inside a self-host stamp. Never a vendor email SDK.
Every record type in your organization is a GraphQL type already; a workflow queries it as a block.
Transcribe, Textract, Bedrock or any AWS API, signed with a key that never leaves the secret store.
A bucket in another AWS account as an nQube S3 block source or sink.
nventr smart routing by default; your own key for $0 in model credits; or the sovereign runner on your own endpoint.
The frontier tier; realtime voice from xAI and OpenAI.
The bulk and strong tiers the router escalates through.
Image and video generation blocks.
Your own endpoint, on your own hardware, as the local tier or the only tier.
Where the Dev Console works, and where a change goes.
The layer repo, the mirror of an app you keep, and the remote reviewed batches are pushed to.
The default Dev Console runtime; or a warm pool; or the sovereign runner on your own model endpoint.
An app you keep with a Dockerfile is built and run as a container beside the console; your own pipeline otherwise.
Desktop and mobile shells around the same app, as the native bundles on pricing.
Every instance is an MCP server; the same tools as the in-app assistant, under the member’s seat, audited.
Because the honest unit is the mechanism, not the brand. A system you reach through a declared REST call works whether or not we have drawn its logo; one we cannot reach today is listed as “ask us”, not hidden.
Yes. An App Kit instance runs on native Azure — Container Apps, Blob Storage, Key Vault, Container Registry, Log Analytics, Azure Database for PostgreSQL and Communication Services Email, selected by one switch (CLOUD_PROVIDER=azure) — or as sealed images on a VM in your subscription, and the plane hosts instances on Azure VMs. Microsoft identity (Entra ID), SharePoint, Teams and Microsoft 365 mail work on either cloud. nventr.io itself runs on AWS.
Dropbox and Google Drive are knowledge connectors: a folder, synced on a schedule. OneDrive and Box are not today — upload the files, point a crawl at a shared site, or tell us which one you need first on the contact form.
A declared REST or JSON API with the auth it needs. That is the same path for NetSuite, Salesforce, HubSpot, Zendesk, Jira or QuickBooks; the credential stays in the secret store and the call is a capability you declared, so an undeclared write cannot happen.
Yes: the one-VM self-host stamp with Supabase and MinIO, models on vLLM or Ollama, Gitea for git, and the sovereign runner for Dev Console. The license moves with the server.
Need one that is not here? Say which on the contact form; how a declared system is called is on Integrations, and where a workflow may write is on Security.