INDEPENDENT PRODUCT

Foxoko brings backend operations into one controlled workflow

Instead of scattered bots, one-off admin scripts, and undocumented operational steps, Foxoko provides a structured layer for actions, alerts, approvals, and audit across multiple services.

3 Core components
Mobile + CLI Operator interfaces
Approval-ready Critical actions

One operator plane for actions, events, approvals, and history.

Product Structure

Foxoko is built as a compact operations stack: a self-hosted orchestrator, a CLI for setup and administration, and an iOS client for mobile execution and notifications.

Control Orchestrator
Bootstrap appctl CLI
Operate iOS App

What The Product Does

Application Registry

MANIFEST-DRIVEN

Each connected backend is described through a manifest: health checks, available actions, accepted inputs, and outgoing event types. Foxoko uses that manifest to build operational interfaces dynamically.

  • New applications can be introduced without shipping a new mobile client
  • Action controls are generated from the declared schema
  • Operational behavior stays explicit and versionable

Remote Actions

SHELL / HTTP

Foxoko can execute operational commands through shell calls or existing HTTP endpoints, without forcing applications to adopt a new SDK.

  • Works with the interfaces the service already exposes
  • Supports dangerous action confirmation on the client side
  • Allows critical commands to enter an approval cycle first

Approvals And Audit

CONTROL PLANE

Foxoko keeps a record of who acted, what changed, when it happened, how long it took, and whether approval or comments were involved.

  • Role-based access for viewers, operators, and owners
  • Approval flows for critical production actions
  • A durable operational history for both actions and events

Events And Notifications

REAL-TIME

Applications emit events into Foxoko, which routes them through push notifications and live feeds based on manifest-defined rules.

  • Supports structured severity levels and custom fields
  • Delivers alerts directly to iOS through push
  • Keeps post-factum comments tied to the operational record

Device Onboarding

QR-BASED

Operators pair their iOS devices with the server through a QR flow, avoiding manual entry of URLs, tokens, or connection credentials.

  • Fast mobile onboarding for trusted operators
  • Secure token handling on the device side
  • Operational access without brittle manual setup

Where It Fits

Across backend estates

Foxoko gives infrastructure teams a single operational surface across multiple services instead of fragmented control paths.

Above the TRON platform

It can operate as the control layer above BlockMonitor, Proxy Node, Resource Service, Vault Service, and Signer.

Beyond blockchain

The product is deliberately domain-neutral, so the same operating model can be applied to other backend systems.

Operating Model

Flow 01

Register services

The team defines each application through manifests and health endpoints, then exposes actions and event channels without embedding a dedicated SDK.

Stack: Manifest + health checks + event endpoint

Flow 02

Route actions safely

Operators trigger commands from the mobile client, while sensitive operations can require explicit approval before execution.

Stack: Roles + execution + approvals

Flow 03

Track events continuously

Services send operational events to the orchestrator, which pushes them to users and preserves them in a shared history.

Stack: Webhook events + live feed + push

Flow 04

Review the record

Actions, comments, approvals, and results stay tied together in one operational audit trail for teams that need accountability.

Stack: Actor + comment + result + duration

Summary

Delivery

Standalone software with self-hosted server and CLI, plus mobile client distribution.

Deployment Client infrastructure
Commercial Model

License-based delivery, potentially shaped by the number of connected applications and operators.

Billing Deployment license
Differentiation

Manifest-driven interfaces, zero-SDK integration, approval workflows, and auditability in one product.

Positioning Domain-neutral operations layer