> ## Documentation Index > Fetch the complete documentation index at: https://docs.nugen.in/llms.txt > Use this file to discover all available pages before exploring further. # Deploy alignment infrastructure inside your own cloud or cluster > Register your cloud environment or existing Kubernetes cluster. All alignment training, model storage and inference then run within your network boundary. No data leaves your environment. Two paths are supported. **Managed provisioning.** Provide a clean, isolated cloud subscription or project. The system provisions a hardened Kubernetes environment from infrastructure-as-code blueprints, configures GPU scheduling and manages ongoing operations through secure GitOps pipelines. No access to your corporate network is required. **Cluster import.** Point to an existing cluster or namespace. The system deploys a self-contained serving and training stack configured to your constraints: storage classes, ingress rules, identity bindings, registry policies. Updates arrive through private registry syncs, so your security team controls when changes land. Once connected, every endpoint in this platform behaves identically whether it runs on our infrastructure or inside yours. The same alignment workflows, model management, auto-align and export paths work unchanged. The system manages GPU node health, autoscaling, deployment lifecycle and performance within your cluster. **Request Body:** - `cluster_name` (required): Name for this environment - `mode` (required): `managed_provisioning` or `cluster_import` - `cloud` (required): Provider, region and the stored credential reference - `cluster_import` (optional): Kubeconfig reference, endpoint, namespace and node labels. Required when `mode` is `cluster_import` - `config` (optional): gpu, networking, storage, iam, registry, operations, capabilities, compliance, overflow and notifications **Returns:** - `cluster_id`: Identifier of this environment - `cluster_name`, `status`, `message` **Raises:** - `400`: If `mode` is `cluster_import` and no `cluster_import` block is given **Notes:** - Egress is restricted and endpoints are private by default; you open them explicitly - Air-gapped registries are a first-class path, and your team controls the sync cadence - Bring your own cloud is an Enterprise Edition capability. The request is recorded and our team follows up; raise a support ticket to enable it - Poll `GET /byoc/clusters/{cluster_id}/status` for provisioning progress and cluster health ## OpenAPI ````yaml https://api.nugen.in/openapi-public.json post /api/v3/byoc/clusters openapi: 3.1.0 info: title: Nugen Intelligence API description: >+ Nugen Intelligence: Powering Specialized Intelligence At Scale. **Need an API key?** Sign up, log in to the platform and generate an API key. **Need help?** Sign up, log in to the platform and raise a support ticket. **What this API does.** Align models to your domain corpus and run them with confidence. Train-time alignment builds domain-aligned adaptors through proprietary methods spanning pre-training, supervised and reinforcement stages. Inference-time alignment quantifies uncertainty across the full generation trajectory, producing confidence scores and keeping every response on domain. **Workflow.** Upload documents, create or generate a benchmark, create an alignment project, receive an aligned model id. That one id serves chat completions, completions, embeddings and reranking, and its embeddings carry your domain's representation space, making retrieval domain aware. You define the success criteria for your domain; the platform handles the deep learning, the GPUs and the data preparation. **Authentication.** Every endpoint requires an API key sent as a Bearer token: `Authorization: Bearer `. contact: name: Nugen Intelligence - Customer Support url: https://nugen.in/signup email: support@nugen.in version: 25.4.20 servers: - url: https://api.nugen.in description: Production security: [] paths: /api/v3/byoc/clusters: post: tags: - BYOC summary: Deploy alignment infrastructure inside your own cloud or cluster description: >- Register your cloud environment or existing Kubernetes cluster. All alignment training, model storage and inference then run within your network boundary. No data leaves your environment. Two paths are supported. **Managed provisioning.** Provide a clean, isolated cloud subscription or project. The system provisions a hardened Kubernetes environment from infrastructure-as-code blueprints, configures GPU scheduling and manages ongoing operations through secure GitOps pipelines. No access to your corporate network is required. **Cluster import.** Point to an existing cluster or namespace. The system deploys a self-contained serving and training stack configured to your constraints: storage classes, ingress rules, identity bindings, registry policies. Updates arrive through private registry syncs, so your security team controls when changes land. Once connected, every endpoint in this platform behaves identically whether it runs on our infrastructure or inside yours. The same alignment workflows, model management, auto-align and export paths work unchanged. The system manages GPU node health, autoscaling, deployment lifecycle and performance within your cluster. **Request Body:** - `cluster_name` (required): Name for this environment - `mode` (required): `managed_provisioning` or `cluster_import` - `cloud` (required): Provider, region and the stored credential reference - `cluster_import` (optional): Kubeconfig reference, endpoint, namespace and node labels. Required when `mode` is `cluster_import` - `config` (optional): gpu, networking, storage, iam, registry, operations, capabilities, compliance, overflow and notifications **Returns:** - `cluster_id`: Identifier of this environment - `cluster_name`, `status`, `message` **Raises:** - `400`: If `mode` is `cluster_import` and no `cluster_import` block is given **Notes:** - Egress is restricted and endpoints are private by default; you open them explicitly - Air-gapped registries are a first-class path, and your team controls the sync cadence - Bring your own cloud is an Enterprise Edition capability. The request is recorded and our team follows up; raise a support ticket to enable it - Poll `GET /byoc/clusters/{cluster_id}/status` for provisioning progress and cluster health operationId: create_byoc_cluster requestBody: content: application/json: schema: $ref: '#/components/schemas/BYOCClusterRequest' required: true responses: '202': description: Bring your own cloud request accepted and recorded. content: application/json: schema: $ref: '#/components/schemas/BYOCClusterResponse' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - HTTPBearer: [] components: schemas: BYOCClusterRequest: properties: cluster_name: type: string title: Cluster Name description: Name for this environment, used across status, logging and billing. examples: - prod-alignment-cluster mode: type: string enum: - managed_provisioning - cluster_import title: Mode description: >- managed_provisioning builds a hardened Kubernetes environment from a clean cloud subscription. cluster_import deploys the alignment and serving stack into a cluster you already run. cloud: additionalProperties: true type: object title: Cloud description: >- Provider, region and the stored credential reference. Determines which provisioning blueprints and identity paths are used. cluster_import: anyOf: - additionalProperties: true type: object - type: 'null' title: Cluster Import description: >- Kubeconfig reference, endpoint, namespace and node labels. Required when mode is cluster_import. config: anyOf: - additionalProperties: true type: object - type: 'null' title: Config description: >- Optional settings for gpu, networking, storage, iam, registry, operations, capabilities, compliance, overflow and notifications. Egress is restricted and traffic is private by default, and anything omitted resolves to auto. type: object required: - cluster_name - mode - cloud title: BYOCClusterRequest description: >- Register a cloud environment or an existing cluster to run in. Only the name, the mode and the cloud block are required. Every other section is accepted as given and stored verbatim, so an environment can pin any detail without the public schema enumerating every knob. BYOCClusterResponse: properties: cluster_id: type: string title: Cluster Id description: Identifier of this environment. cluster_name: type: string title: Cluster Name description: Name given to the environment. status: type: string title: Status description: Request status. message: type: string title: Message description: Human-readable outcome of the request. type: object required: - cluster_id - cluster_name - status - message title: BYOCClusterResponse description: Acknowledgement of a bring your own cloud request. HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: HTTPBearer: type: http scheme: bearer ````