RT
Active ToDy95/OmniInfra

OmniInfra

Private infrastructure visibility and delivery control room

Bring application health, deployments, infrastructure usage, and operational evidence into one protected control room for teams running several services.

Latest signal

Nov 15, 2026

Synced Nov 16, 2026

76

Commits · 365 days

51

Pull requests · 365 days

0

Issues · 365 days

0

Code reviews · 365 days

Public summary

Public summary

What it is

OmniInfra is a private control room for operating several applications and their supporting services. It brings project navigation, observed health, deployment state, infrastructure measurements, and operational evidence into a protected workspace.

It is relevant to technical founders and small engineering teams that own their hosting and need a clearer view of what is running and what changed.

The problem and business value

A growing application portfolio can spread operational knowledge across terminals, provider consoles, and deployment notes. That makes routine questions harder to answer: which release is active, where a failure occurred, and what evidence exists for recovery.

OmniInfra organizes those questions around the application and its environment. The intended value is more informed maintenance and a traceable delivery process. It does not promise uninterrupted service or replace an agreed support arrangement.

What it does today

  • Provides protected project and environment navigation alongside application, deployment, and incident views.
  • Collects bounded host, container, and database metadata for infrastructure visibility.
  • Separates the host collector from web processes that have no Docker control access.
  • Supports registered delivery pipelines with checks, bounded builds, revision validation, and release evidence.
  • Provides operational runbooks, backup tooling, and documented recovery exercises.
  • Integrates scoped secret-management operations through a protected server-side service.

Integrations and data flow

A host-side collector produces bounded infrastructure snapshots. Protected services serve those snapshots and scoped provider metadata to the control room. HTTPS and a shared two-factor access gate protect administration surfaces.

Automatic application delivery uses a read-only GitHub App and an explicitly registered project list. A repository's existence does not enroll it for deployment. Builds and promotion follow the registered pipeline, with source identity checked before release.

AI or automation workflow

Collection and registered delivery are deterministic operational workflows. Proposed research or autonomous maintenance programmes are separate from the deployed system. An assistant recommendation does not authorize a restart, deletion, secret change, or production release.

Collaboration and privacy

The control room is an owner/operator surface. It does not expose raw application logs, credentials, backup archives, or customer table contents in the public portfolio. Private infrastructure addresses and administration links are intentionally omitted here.

What is coming next

Recovery verification can be extended across more application stacks, and reporting can grow around actual operator needs. A verified restore of a particular backup is evidence for that exercise, not proof that every application can recover end to end.

Current activity and next step

The repository includes the portal, fixed collector paths, delivery workers, checks, and dated release evidence. Recent delivery work documents automatic releases for the registered application set. No customer uptime, cost reduction, or full disaster-recovery guarantee is claimed.

Discuss your application operations. Start with your services, the operational question you cannot answer easily, and the deployment or recovery process you want to make reviewable.

Contribution graph

The work behind the work.

Commits, PRs, issues and reviews

127 recorded activities in the selected range.

All available activity

LessMore
Monthly activity totals
Recorded activity for the selected range, grouped by month
MonthActivities
2025-110
2025-120
2026-010
2026-020
2026-030
2026-040
2026-050
2026-060
2026-070
2026-080
2026-090
2026-1057
2026-1170

Recent activity

What is moving now.

  1. docs: add public infrastructure sales portfolio briefCommit · Nov 15, 2026↗
  2. docs: add public infrastructure sales portfolio briefPull request - merged · Nov 15, 2026↗
  3. Record verified automatic delivery for all nine applicationsPull request - merged · Nov 14, 2026↗
  4. docs: record nine-project automatic deployment verification (#50)Commit · Nov 14, 2026↗
  5. Fit Portfolio coverage to bounded VPS test resourcesPull request - merged · Nov 14, 2026↗
  6. fix: bound Portfolio checks to the VPS CPU budget (#49)Commit · Nov 14, 2026↗
  7. Enable Portfolio main-triggered VPS deploymentPull request - merged · Nov 14, 2026↗
  8. feat: enable rehearsed Portfolio main delivery adapter (#48)Commit · Nov 14, 2026↗
  9. Add durable Portfolio automatic delivery adapter (#47)Commit · Nov 14, 2026↗
  10. Add durable Portfolio automatic delivery adapterPull request - merged · Nov 14, 2026↗
  11. fix: reconcile legacy portfolio workflow migration receiptsPull request - merged · Nov 14, 2026↗
  12. fix: reconcile legacy portfolio workflow migration receiptsCommit · Nov 14, 2026↗
  13. fix: verify portfolio ingress after graceful proxy signalsPull request - merged · Nov 14, 2026↗
  14. fix: verify portfolio ingress after graceful proxy signalsCommit · Nov 14, 2026↗
  15. fix: serialize runtime credentials and launch the health bridgePull request - merged · Nov 14, 2026↗
  16. fix: serialize runtime credentials and launch the health bridgeCommit · Nov 14, 2026↗
  17. fix: bound VPS test worker concurrency (#43)Commit · Nov 14, 2026↗
  18. fix: bound VPS test worker concurrencyPull request - merged · Nov 14, 2026↗
  19. feat: prepare durable application admission controlsPull request - merged · Nov 14, 2026↗
  20. feat: prepare durable application admission controls (#42)Commit · Nov 14, 2026↗

Published roadmap

What is shipped and what comes next

Delivered

  • [done] Protected application and infrastructure control room.
  • [done] Registered host-pull delivery with revision checks and release evidence.

Operationally pending

  • [in-progress] Broaden end-to-end recovery verification across application stacks.

Coming soon

  • [planned] Expand reporting from verified operational needs.

Discuss the next step. Scope, account access, and readiness are agreed before implementation or rollout.