Product Overview

What Eco Manager Is

Eco Manager is a self-hosted technical asset directory with secure credential management and planned remote access.

It is designed for BMS commissioning, telecoms operations, remote support, and technical estate management teams that need a reliable source of truth for:

• what equipment is installed,
• where it is installed,
• how it is configured,
• which credentials are needed to work on it,
• who accessed it,
• and how engineers can securely reach it remotely.

Eco Manager is the technical operations layer between engineers, customer sites, assets, credentials, audit records, integrations, and remote access workflows.

The Three Product Pillars

1. Directory

The Directory is the structured record of managed technical environments.

The default hierarchy is:

Customer
└── Site
    └── Building
        └── Asset

The architecture is intentionally flexible. Future hierarchy levels such as Room, Floor, Cabinet, Network Zone, or Panel can be introduced without redesigning the database.

Assets and other entities can have:

• typed properties,
• property groups,
• tags,
• tag groups,
• entity groups,
• relationships,
• templates,
• audit events,
• attachments,
• notes,
• workflow state.

2. Credentials and Secrets

The Vault manages sensitive values such as:

• passwords,
• API keys,
• PINs,
• private keys,
• device secrets,
• remote access credentials.

Secrets are not ordinary editable properties. The Vault is the sole authority for writing, rotating, revealing, and auditing secrets.

Secret metadata may appear in directory views, but decrypted secret values are only revealed through controlled Vault operations.

Sensitive values are protected by tenant/root-level encryption boundaries so data belonging to one organisation or customer scope cannot be decrypted from another scope.

3. Remote Connectivity

Remote Connectivity is planned for Beta.

A lightweight site agent will establish an outbound tunnel from a customer network to the Eco Manager Hub. An engineer Companion app will connect through the Hub and launch tools such as:

• RDP,
• SSH,
• VNC,
• BACnet tools,
• vendor engineering tools.

The aim is to provide remote access without exposing credentials directly to engineers or requiring inbound firewall openings at customer sites.

Additional Application: Admin Studio

Eco Manager includes an internal Admin Studio app for platform administrators and trusted super users.

Admin Studio is a full CRUD interface over the Universal Entity Platform. It is conceptually closer to Notion or Obsidian than to a traditional back-office table editor: users can navigate entity types, entities, property groups, tag groups, templates, relationships, and groups as interconnected knowledge objects.

Admin Studio is not the normal engineer workflow UI. It is the advanced configuration and administration surface used to manage the platform model itself.

What Eco Manager Is Not

Eco Manager is not a field service management platform.

Systems such as Simpro remain responsible for:

• jobs,
• scheduling,
• dispatch,
• quoting,
• invoicing,
• SLA tracking,
• customer-facing reports.

Eco Manager owns the technical asset truth, credential vault, secure access path, configuration model, and operational audit trail.

Simpro Owns	Eco Manager Owns
Job scheduling	Technical asset directory
Work orders	Asset configuration and properties
Billing	Encrypted credentials
Quoting	Secure remote access paths
SLA tracking	Technical audit trail
Customer-facing reports	Asset health and commissioning state

Architecture In One Sentence

Eco Manager is a contract-driven modular monolith built with Bun, Hono, React, TanStack Router/Query, Drizzle ORM, PostgreSQL, Zod, and a Universal Entity Platform at its core.