Billing, payments, domains, DNS, and network bridges

Organization-scoped features that touch money, names, and network plumbing.

Billing

Payment methods

• Add and manage cards or SEPA mandates (provider-dependent).
• Mark a primary payment method for automatic charges.

Invoices

• List and download invoices issued to the organization.
• Payment terms (anchor day, due days) live on the organization record.

Spending controls

• Organization and project levels may expose spending limits and warning thresholds with optional email notifications when crossed.

Agreements & pricing overrides

• Operators may attach billing agreements that adjust display prices for compute profiles (e.g. committed use discounts).

Cost summaries

• Where exposed, cost summary endpoints aggregate spend visibility for the organization (detail depends on billing integration).

Domains

Domains represent DNS domains Loopback tracks for your organization — used when creating DNS zones, workspace hostnames, or load balancer frontends.

Workflow is usually:

1. Register or prove ownership of a domain (outside Loopback or via integration).
2. Attach domain records in Loopback so delegation and automation can create records safely.

DNS records and DNS record zones

DNS record zones define allowed patterns (wildcards) for records created under a domain, optionally scoped to a project or workspace. This prevents one team from claiming another’s hostname namespace.

DNS records are individual A/AAAA/CNAME/… entries Loopback synchronizes to providers (e.g. Cloudflare) based on configuration.

User impact

• Workspace creation may allocate *.k8s.<operator-domain> automatically.
• Custom APIs may use zones you delegate for *.api.example.com.

Network bridges

Network bridges link network segments (e.g. join workspace networks for hybrid scenarios). Behavior is operator-specific; use this when your architecture doc mentions bridged or peered Loopback networks.

Related reading

• Organizations overview
• Project DNS zones
• Workspace overview