Skip to main content
Ottili Cloud

Domains and TLS

How custom domains, DNS and TLS are planned in Ottili Cloud (Early Access) — and what status applies today.

Overview

Domains and TLS are the infrastructure that makes your Ottili Cloud resources reachable under your own addresses: you attach a custom domain, resolve it through DNS, and protect the transport with TLS. In Ottili Cloud, domains and TLS are part of the Early Access build-out — the capability is shown on the public Cloud page, but self-service is not yet generally orderable.

This page describes the intended model and the honest status. Where a procedure depends on a service that is not yet live, we say so clearly instead of describing a step that does not exist yet.

What domains and TLS include

  • Custom domains*: you run your cloud resources under a domain you control, rather than only through Ottili addresses.
  • DNS*: name resolution for your services — domains and subdomains point at your cloud resources.
  • TLS*: encrypted transport for reachable traffic; the platform provides TLS at the edge so HTTPS is used for delivered content.

How domains and TLS relate to networking and regions

Domains build on networking: an instance or a load balancer joins a virtual network, and DNS resolves the name clients use. Regions determine where the resource lives, and therefore where it is reachable. A domain is bound to the same company-scoped project as the resource it serves.

Status at a glance

  • Ottili Cloud (product)*: Early Access — pre-release, not generally available.
  • Domains (custom domains, DNS)*: Early Access / In development — capability shown on the public Cloud page; self-service not yet orderable.
  • TLS (edge transport encryption)*: In development — TLS at the edge for delivered traffic; customer-managed certificates are not yet a self-service feature.
  • Networking, compute, storage*: see the respective articles — compute is reachable today through Early Access; storage and networking are planned.

We do not claim specific certificate authorities, SLAs or pricing that are not yet defined, and we do not publish internal service paths or private API routes in public docs.

Related

  • The foundation is [Ottili Cloud](/docs/ottili-cloud).
  • Networking and DNS connect through [Networking](/docs/cloud-networking).
  • Transport encryption and the model are covered under [Security](/docs/cloud-security).
  • Where resources live is governed by [Regions](/docs/cloud-regions) and [Compute](/docs/cloud-compute).

For the product overview and Early Access, see [Ottili Cloud](/cloud).

Was this article helpful?