Skip to navigation
Operate at scale

Bring your own cloud (BYOC)

BYOC lets an Enterprise customer run a dedicated Talqora Vector deployment in its own AWS account. Data, network boundaries, and infrastructure ownership remain in the customer account; Talqora supplies the reviewed Terraform module and operates the Talqora cluster software.

Availability

BYOC is available only on Enterprise plans. We can target an AWS Region selected by your team, subject to availability of the AWS services required by the deployment in that Region and your account quotas.

The normal public API origin remains https://api.talqora.com. An Enterprise deployment can additionally receive a regional API alias when needed for network topology or latency. See Regional API endpoints.

What Talqora manages

Talqora’s operational scope is intentionally narrow:

  • Cluster software updates and compatibility upgrades.
  • Cluster health, telemetry, alerts, and observability.
  • Release coordination and incident diagnosis for the Talqora-managed components.

Talqora does not take ownership of your AWS account, application data, IAM administration, network policy, billing, or unrelated cloud resources. Your team retains control of the Terraform state, account access, data-retention policy, and AWS security controls.

Terraform delivery

After architecture review, Talqora provides a versioned Terraform module and an environment-specific variables file. Your platform team applies it from its own CI/CD identity and state backend.

module "talqora_vector" {
  source  = "talqora/vector/aws"
  version = "~> 1.0"
  name        = "talqora-production"
  aws_region  = "sa-east-1"
  environment = "production"
  # Customer-owned network and encryption boundaries.
  vpc_id             = aws_vpc.platform.id
  private_subnet_ids = aws_subnet.private[*].id
  kms_key_arn        = aws_kms_key.talqora.arn
  observability = {
    cloudwatch_log_retention_days = 30
    metrics_sink                  = "customer-cloudwatch"
  }
}

The exact inputs depend on the approved topology. The module validates the chosen Region and required service availability before provisioning customer workloads.

Engagement flow

  1. Contact Talqora with the AWS account, Region, network model, and compliance requirements.
  2. We review the target topology, IAM boundaries, quota requirements, and observability integration.
  3. Talqora delivers the pinned Terraform module and deployment runbook.
  4. Your team applies the module in its own account and validates connectivity.
  5. Talqora enables ongoing cluster updates and observability for the deployed Talqora components.

For an Enterprise BYOC architecture review, contact Talqora before creating production infrastructure.