Nomain Docs

Appearance

Nomain Cloud (SaaS) ​

Nomain Cloud is the hosted, multi-tenant version of the platform, operated by Nomain on Microsoft Azure. It is the fastest way to start: there is no infrastructure for you to provision, deploy, or run. You sign in, connect your repositories, and begin.

What Nomain operates for you ​

On Nomain Cloud, Nomain runs and maintains the entire stack:

  • The application services, databases, object storage, and the analysis pipeline.
  • The Azure OpenAI foundation models the platform uses.
  • Upgrades, scaling, monitoring, and backups.

Your organization is provisioned as a tenant. Each tenant's data (chat history, knowledge graphs, repository metadata, and embeddings) is isolated in its own per-tenant database and scoped by tenant ID, so one customer's data is never visible to another.

What you do ​

Getting productive on Nomain Cloud takes three steps:

  1. Invite your team. An administrator adds users from the Users screen. People receive an email to set up their own account.
  2. Set up single sign-on (optional). Connect Okta, Entra ID, Auth0, or Keycloak yourself from the Account screen. See Single sign-on.
  3. Connect your code. Add a Git or SFTP repository and create a System from it.

That is all. There are no servers, model deployments, or quotas for you to manage.

Sign-in and security ​

End-user sign-in uses WorkOS AuthKit, the same identity layer as every other deployment model, so your users authenticate through your existing identity provider. Nomain stores no end-user passwords, and authentication is delegated to your IdP.

When to choose Nomain Cloud ​

Choose Nomain Cloud when...Consider BYOC instead when...
You want to evaluate Nomain quickly, with nothing to provision.Your code or analysis must stay inside your own cloud tenant.
You do not have (or do not want to involve) a cloud platform team.You have data-residency, sovereignty, or regulatory requirements that mandate a customer-controlled data plane.
A Nomain-operated service fits your risk posture.You need full physical isolation or an air-gapped deployment.

If your requirements point toward keeping everything in your own perimeter, move to BYOC on Azure, BYOC on AWS, or on-premise. The product experience is identical.