Deploy an agent
into an isolated runtime.

Core model

Three resources stay deliberately separate. This distinction makes builds reproducible and production promotion safe.

Create and promote

1. 1

   Choose a source

   Templates are the default and fastest path. You can also provide a Dockerfile archive or attach Git metadata.

2. 2

   Configure required secrets

   A template declares exactly which runtime values it needs. Required fields appear before project creation and are stored encrypted.

3. 3

   Prepare the deployment

   Templates reuse a validated build and become ready_to_promote immediately. Custom archives run through the full build pipeline.

4. 4

   Promote deliberately

   Talqora starts the validated version and atomically points the project hostname to it.

Operate the complete lifecycle from a terminal

The CLI is a dependency-light Python 3 executable for macOS and Linux. The installer places it in ~/.local/bin/talqora; set TALQORA_BIN_DIR or TALQORA_INSTALL_DIR to choose another location.

curl -fsSL https://talqora.com/install.sh | sh

talqora login
talqora status

How browser login works

1. 1

   Request

   talqora login creates a random device secret and a human-readable code that expire after ten minutes.

2. 2

   Approve

   The CLI opens talqora.com/cli/authorize. Sign in to the dashboard and approve the named terminal. Your password and browser session never enter the CLI.

3. 3

   Exchange once

   The terminal polls the control plane and receives a user-bound credential once. The temporary encrypted copy is deleted during that exchange.

4. 4

   Revoke

   Run talqora logout --revoke, or revoke the CLI credential from Organization API keys. A plain logout only removes the local file.

talqora --help
talqora projects --help
talqora --json api GET /api/projects

Configured per project, built once

A ready template is an immutable application build maintained by Talqora. Creating a project from it does not rebuild dependencies. Each project still receives its own isolated runtime and public hostname.

What your archive must provide

Upload a zip whose root contains a Dockerfile. The application must listen on port 8080 and support the Talqora lifecycle handlers.

FROM python:3.12-slim
WORKDIR /app
COPY . .
RUN pip install -r requirements.txt
EXPOSE 8080
CMD ["python", "server.py"]

One credential, one organization

Every API key belongs to exactly one organization. Send it as a bearer credential or with X-Talqora-Key. The same project and deployment endpoints also accept dashboard session tokens.

export TALQORA_API_KEY="tq_live_..."

curl https://api.talqora.com/api/projects \
  -H "Authorization: Bearer $TALQORA_API_KEY"

Create, use, rotate, revoke

1. 1

   Create

   Open Organization settings → API keys, name the credential, and create it. Key management requires an owner or admin dashboard session; an API key cannot create more keys.

2. 2

   Store once

   Copy the tq_live_... value immediately. Talqora cannot reveal it again.

3. 3

   Use

   Call any project or deployment endpoint. Authorization is automatically scoped to the key's organization.

4. 4

   Rotate

   Create a replacement, update the client, verify traffic through last_used_at, then delete the old key.

Endpoint reference

The API base URL is https://api.talqora.com. JSON request bodies require Content-Type: application/json.

curl https://api.talqora.com/api/projects \
  -X POST \
  -H "Authorization: Bearer $TALQORA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "weather-agent",
    "source_type": "dockerfile_upload",
    "git_branch": "main",
    "runtime_idle_timeout_seconds": 1800
  }'

Suspend and activate safely

Runtime controls operate on the project's currently promoted instance. Talqora verifies organization ownership, keeps the production hostname attached, and records the requested state for the dashboard.

curl -X POST \
  https://api.talqora.com/api/projects/$PROJECT_ID/runtime/suspend \
  -H "Authorization: Bearer $TALQORA_API_KEY"

{
  "instance_id": "2b63fb24-...",
  "state": "suspended",
  "state_reason": "Suspended manually"
}

curl -X POST \
  https://api.talqora.com/api/projects/$PROJECT_ID/runtime/resume \
  -H "X-Talqora-Key: $TALQORA_API_KEY"

{
  "instance_id": "2b63fb24-...",
  "state": "pending",
  "state_reason": "Activation requested manually"
}

Read a deployment's operational view

The logs endpoint merges durable platform events with available build output, runtime stdout/stderr, request telemetry, and resource samples. It returns a snapshot, not a streaming connection.

curl "https://api.talqora.com/api/deployments/$DEPLOYMENT_ID/logs?limit=200" \
  -H "Authorization: Bearer $TALQORA_API_KEY"

Blue-green at the routing layer

The replacement runtime is started and checked before one atomic route update. A failed build or launch never replaces the current production version.

One hostname per project

Every promoted project is reachable at https://slug.live.talqora.com. Paths, methods, query strings, request bodies, and safe headers are forwarded to the active runtime.

Pause idle capacity per project

Every project owns an inactivity threshold from five minutes to eight hours. The value is measured from public endpoint traffic and is applied when a runtime is promoted. Changing it does not mutate an already active runtime.

Understand resource pressure

Talqora captures a runtime resource sample after a public request completes. The deployment page checks for stored updates every five seconds; opening or refreshing the page does not create a sample.

Deployment states

Terminal failure states are build_failed, validate_failed, and promote_failed. Replaced production versions become superseded.

Current boundaries

• One promoted runtime and one slug.live.talqora.com route per project
• Manual promotion after every ready template or successful custom build
• Template and Dockerfile sources are functional; Git metadata is stored but cloning and webhook automation are not enabled
• Project-specific custom domains and preview deployments are not enabled yet
• HTTP request proxying; WebSocket forwarding is not implemented yet