Operations and trust

Private beta needs visible operations, not silent hope.

Teleza's beta console and API contracts are designed to show health, provider readiness, usage, failures, onboarding activity, and customer evidence before a design partner depends on the service.

Health and readiness

Hosted and private deployments expose health checks for API, database, provider, and memory status.

Provider visibility

Provider Ops tracks readiness for InMemory, REST, PostgreSQL, SQL Server, CSV, Excel, email transport, and runtime configuration.

Usage evidence

Customer usage, failed executions, daily ledger rows, API-key prefixes, and activity evidence can be reviewed without exposing secrets.

Operator console coverage

  • Provider Ops summary for status, database timing, provider readiness, errors, slow reports, rate pressure, and runtime posture.
  • Beta Requests triage with notification status, customer conversion, one-step onboarding, and pilot outcome tracking.
  • Customers and API Keys for scoped key generation, regenerate-and-email, suspension, and usage review.
  • Reports inventory for customer report auditing and guarded delete actions.
  • Activity Log, Error Logs, and Scheduled Jobs for operational review without shell access.
  • Billing and Usage review for usage-backed invoice preparation during private beta.

Customer self-service direction

The Account Console is the customer-facing operations surface: account context, usage evidence, failed-execution visibility, API-key lifecycle controls, branding, and profile/password self-service for customer-bound users with the right permissions.

Team and permission features are scoped to private beta. Roles, invitations, and audit records support the customer model, but production support terms are agreed per pilot.

Trust boundary

Teleza publishes what it can support today: scoped keys, bounded providers, write-only secrets, payload render, template validation, release checks, and private-cloud deployment options. Formal certifications, dedicated infrastructure, strict SLAs, and regulated-industry commitments are negotiated separately.

Read security posture Read resource profile Request pilot review

Resource profile evidence

The local resource-profile rehearsal renders a representative starter-template set and records elapsed time, CPU time, peak memory, output sizes, and document-family coverage. This gives private-beta reviewers a measured sizing baseline without pretending local evidence is a hosted concurrency SLA.

powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\New-ResourceConsumptionManifest.ps1 powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\Test-ResourceConsumptionManifest.ps1

Hosted render-load evidence

The VPS evidence path can run a bounded API-level render batch against POST /api/whiteLabelEngine/v1/render with a disposable scoped API key. It captures health before and after, preview lineage hashes, PDF output artifacts, render latency, output bytes, and sanitized failure categories.

The target render-load script is opt-in because it writes usage and payload-render telemetry on the deployed API. It supports private-beta release decisions; it is not a public throughput guarantee.

powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\Test-TargetRenderLoadEvidence.ps1 ` -ApiBaseUrl "https://api.teleza.tech" ` -ApiKey "sk_live_..." ` -AllowTargetMutation

Render lineage evidence

Payload preview responses include a sealed lineage manifest with lineage.contractHash, template schema version, design theme, mapping key, hashed field map, formatting/grouping/masking option hashes, normalized columns, row count, and generated-at time. The manifest is intended for support, pilot evidence, and replay discussions without embedding raw customer rows.

Completed payload renders persist the same lineage fingerprint in execution telemetry. Customer usage evidence and Provider Ops slow-report review can therefore reference a stored lineageContractHash after the PDF, Excel, or JSON export has completed.

Docker deployment posture

  • Teleza's VPS beta path runs the API in Docker behind Caddy at api.teleza.tech.
  • The container listens internally on port 8080 and is bound to loopback host port 8587 for reverse-proxy access.
  • The runtime image pins explicit .NET 10/Ubuntu image tags instead of latest.
  • The API process runs as a non-root service user after package installation.
  • Generated documents are response artifacts; persistent state is kept in the mounted /data volume, while /tmp is volatile scratch space.