ChiRi Studio
    Booting local-first edge security…
    HQ-Lite | Local-first defensive edge appliance

    Local-first defensive edge security, built for real networks.

    HQ-Lite is ChiRi Studio's purpose-built Linux-based defensive edge appliance. It sits inline between WAN and LAN, combining high-speed network visibility, local device and network context, verified intelligence and Guardian — our bounded Digital Brain for explainable, controlled defensive decisions.

    Core operation remains local. The management dashboard stays inside the protected network, and HQ-Lite does not depend on a public SaaS control plane for core defensive operation.

    inline WAN → LAN LAN-only management local-first bounded decisions long-run field validation
    What is HQ-Lite?

    More than a dashboard. More than a traditional router.

    HQ-Lite is an integrated defensive edge system built around a hardened Linux platform. It takes the network-edge position between the internet connection and the local network, where it can observe network activity, maintain local context, operate core network services and support controlled defensive action.

    Instead of relying on endpoint agents for core edge visibility, HQ-Lite works from its position in the network. The local dashboard brings network state, security events, device context, system health and defensive decisions into one operator-facing interface.

    External network

    Internet / WAN

    Normal internet traffic reaches the protected environment through HQ-Lite.

    Local appliance

    HQ-Lite

    Network services, edge visibility, local context, Guardian decision logic and controlled enforcement are kept together at the network edge.

    XDP EdgeGuardianIOCBlackholeRTSEcho-ProbeWatchdogNoctilux
    Threat Verification Layer — in development.
    Controlled external intelligence path; not a public SaaS control plane for the customer network.
    Protected network

    LAN devices & services

    Clients continue to use the local network while HQ-Lite provides edge visibility and local defensive context.

    Deliberately bounded architecture. Observation, context, assessment, explanation and enforcement are separated so that an event is not turned into an automatic verdict without evidence and policy.
    Guardian — the Digital Brain of HQ-Lite

    A bounded decision engine for the network edge.

    Guardian is HQ-Lite's purpose-built local decision and response engine. It is not an LLM, chatbot or prompt-driven generative AI assistant. Guardian observes relevant network and security behaviour, combines that observation with local context and verified intelligence, assesses risk, explains why an event matters and coordinates a controlled defensive response when policy and operating mode permit it.

    Digital Brain is ChiRi Studio's architectural term for this bounded process — not a claim of unrestricted autonomous AI.

    Observe

    Relevant traffic, device, network and security context.

    Context

    Understand where the event occurred and what local state is relevant.

    Assess

    Evaluate severity, evidence, policy and confidence.

    Explain

    Record why something was flagged and what evidence supports it.

    Decide / Act

    Observe, allow, review or apply an approved local response with an auditable trail.

    No magic-box promises. HQ-Lite is designed to improve defensive visibility, context and controlled response. ChiRi Studio does not claim that any single appliance can stop every cyber threat.
    Inside HQ-Lite

    Core modules with clear, separate responsibilities.

    The core feature set is closed. Current work is focused on integration, validation and the next intelligence architecture rather than open-ended feature growth.

    Discovery

    Discovery IPv4

    Maintains IPv4 network context, interfaces, addressing and protected local state so defensive decisions are applied in the correct network environment.

    Discovery

    Discovery IPv6

    Maintains IPv6 and prefix context so dual-stack operation is understood deliberately rather than treated as unknown external activity. IPv4-only remains a valid operating mode.

    Edge

    XDP Edge

    High-speed visibility and a controlled enforcement path close to the network interface, before selected traffic travels further through the normal network stack.

    Intelligence

    IOC / DNS Policy

    Shows DNS, URL and IP security indicators while keeping candidate observations visibly distinct from stronger confirmed intelligence.

    Containment

    Blackhole

    Dynamic containment for authorised hostile-source decisions. Approved entries can be synchronised with the XDP/eBPF blocking map and removed again when their TTL expires.

    Analysis

    RTS

    Analyses real-time traffic patterns and produces reviewable findings and recommendations, including scanning and abnormal connection-pressure patterns.

    Context

    Region / TOR

    Adds geographic, ASN and TOR context to observations. Context is evidence — not automatic proof of malicious intent.

    Integrity

    Watchdog

    Monitors the operational integrity of HQ-Lite itself: services, processes, admin access, SSH/SFTP behaviour and protected system areas.

    Network identity

    Echo-Probe

    Builds operator-facing device identity and network context, separating trusted devices from observations and helping the administrator understand what is present on the LAN.

    Health

    Noctilux

    Local hardware and system-health visibility: CPU, RAM, storage, temperatures, disk activity and process usage for long-running appliance reliability.

    Network services

    DHCP & Firewall

    Local network services and policy controls required for an inline edge appliance, including DHCP state, reservations and controlled firewall configuration.

    Local memory

    Guardian Memory

    Guardian maintains local Short Memory and Long Memory for the network it protects. Internal intelligence databases are not exposed as general operator databases.

    Interactive HQ-Lite Demo

    Explore the interface without connecting to a live network.

    The standalone demo mirrors the current dashboard structure and operator workflows while using synthetic demonstration data. Visitors can explore Guardian activity, XDP Edge, Blackhole, IOC, RTS, Region/TOR, Echo-Probe, Noctilux, Watchdog and network controls without access to a real HQ-Lite deployment.

    HQ-Lite Standalone Demo v0.4.1 — synthetic data
    Open full demo

    Demo disclaimer: interactive simulation using synthetic demonstration data. No live customer, household or private network data is displayed. The demo is not connected to a live HQ-Lite node, and actions shown in the interface do not affect a real network.

    Threat Verification Layer — current development priority

    Treat security signals as candidates, not automatic truth.

    HQ-Lite is being prepared for a controlled Verified Threat Intelligence Pipeline. The purpose is to stop raw feeds or isolated local observations from becoming automatic enforcement truth.

    A security observation can begin as a candidate. The protected Threat Verification Layer is designed to classify the signal, add context, verify current relevance where appropriate and prepare controlled intelligence packages for local use by HQ-Lite.

    Candidate

    A security-relevant observation enters the verification path.

    Classify

    Identify what the signal is and separate evidence types.

    Verify

    Check relevance, current state and supporting context where appropriate.

    Package → Local use

    Prepare controlled intelligence for HQ-Lite without turning raw input into automatic truth.

    Protected backend. Public documentation describes the trust model and outcome. Internal backend topology, protected trust mechanisms, service roles and verification implementation are not published.
    Plain-English term

    What is a Threat Candidate Event?

    A Threat Candidate Event is a security-relevant network observation that may deserve verification. It is not the same thing as a confirmed threat.

    Examples include a URL that appears to imitate a trusted service, a suspicious domain associated with scam/phishing behaviour, an IP or traffic pattern associated with scanning or repeated probing, or a local observation that matches existing intelligence but still needs local context.

    Privacy & Data Handling

    Local-first security should not mean hidden surveillance.

    HQ-Lite is designed around data minimisation and local operation. Its purpose is to understand network and security context, not to collect the private content of users' online activity.

    What HQ-Lite can process locally

    • IP and network-addressing context
    • DNS/domain and security-indicator context
    • Connection and protocol metadata needed for defensive decisions
    • Device and local-network context
    • Local system-health and security events

    What HQ-Lite is not designed to collect/export

    • Passwords and login credentials
    • Authentication tokens and session secrets
    • Private message or email contents
    • Banking credentials or payment-card details
    • Personal files
    • Phone numbers or email addresses when not required for the security event

    What may leave the node in future controlled workflows

    • Minimal service heartbeat / version / health information
    • Sanitised Threat Candidate Events
    • Only information permitted by the outbound sanitisation and policy layer
    Sensitive-data boundary. The outbound event path is being designed so sensitive fields are rejected or redacted before a security event is eligible for external submission. This is a technical control in development, not only a policy statement.
    No routine TLS interception requirement. HQ-Lite is not designed to depend on TLS interception for its core network-edge visibility model.
    Real-world validation

    Built and tested as the real edge device — not only as a lab dashboard.

    HQ-Lite has been operated inline on a real multi-device network as an ongoing live validation environment since March 2026. Long-run testing is used to expose issues that short demos miss: service-start behaviour, IPv6 changes, database pressure, thermal limits, false-positive handling, restart/recovery behaviour and interaction between defensive modules.

    Since Mar 2026ongoing live-edge validation
    81 daysdocumented Armed Mode meter run
    ~17.6 Wmeasured Observe Mode average
    ~20.0 Wmeasured Armed Mode average
    Measured power evidence

    Observation Mode

    A 35-day long-run meter record from the current HQ-Lite validation environment.

    35 daysmeasurement period
    14.79 kWhtotal energy
    ~17.6 Wcalculated average
    Power meter showing 14.79 kWh over 35 days during HQ-Lite Observation Mode validation

    Average calculated from the recorded total energy and measurement duration: 14.79 kWh ÷ 35 days ≈ 17.6 W.

    Measured power evidence

    Armed Mode

    An 81-day long-run meter record from the current HQ-Lite validation environment.

    81 daysmeasurement period
    38.82 kWhtotal energy
    ~20.0 Wcalculated average
    Power meter showing 38.82 kWh over 81 days during HQ-Lite Armed Mode validation

    Average calculated from the recorded total energy and measurement duration: 38.82 kWh ÷ 81 days ≈ 20.0 W.

    Current long-run validation platform
    Current HQ-Lite validation platform with HP SFF system and separate TP-Link Archer C6 wireless access point

    Current field-validation setup. The wireless access point is a separate device and is not part of HQ-Lite itself.

    Modest hardware, real edge workload.

    The current HQ-Lite validation node deliberately uses an older small-form-factor x86 platform to test whether the complete edge appliance can remain practical without requiring new or high-end hardware.

    CPUIntel Core i5, 8th generation
    Memory8 GB RAM
    Storage256 GB NVMe
    NetworkIntel X540 dual-port 10GbE RJ45
    CablingCat6A
    Wi-Fi is separate. HQ-Lite does not provide built-in Wi-Fi and does not depend on an internal Wi-Fi adapter for core operation. Wireless access requires a separate access point connected on the LAN side. In the current validation setup, Wi-Fi is provided by a TP-Link Archer C6 configured in Access Point mode.

    This is the current long-run validation platform, not a declaration of final commercial hardware specification. Actual power use can vary with hardware, storage, NIC configuration, workload and network activity.

    Repeatable deployment testing

    Four controlled Clonezilla installation tests completed successfully using two separate HDDs on the reference HQ-Lite appliance, supporting repeatable deployment validation across more than one target drive.

    Long-run appliance discipline

    Power, stability, system health, network services and defensive behaviour are measured over long periods rather than inferred from short laboratory runs.

    The meter photographs document specific long-run test windows; they are not presented as uninterrupted product uptime. Planned interruptions for imaging, controlled backup and mode-transition testing are recorded separately.

    Current status / Roadmap

    Operational now, in development now, and next.

    Operational / validated locally

    HQ-Lite Alpha Core

    • Inline edge operation and LAN-only dashboard
    • Guardian observation, assessment and decision path
    • XDP visibility and controlled enforcement paths
    • IOC, Blackhole, RTS, Region/TOR
    • DHCP / firewall, Echo-Probe, Noctilux and Watchdog
    • Ongoing Armed Mode field validation
    In development now

    Threat Verification Layer

    • Canonical threat-intelligence workflow
    • Controlled intelligence exchange
    • Signed intelligence package workflow
    • Guardian memory / data-model integration
    • Outbound sanitisation and minimal service communication
    • Supporting infrastructure for the next integration stage

    Integration & controlled external validation

    • HQ-Lite integration with the Threat Verification Layer
    • Rollback and operational-safety testing
    • Repeatable installation image / deployment preparation
    • Controlled external field validation on trusted test networks
    • Structured pilot readiness only after the technical path is proven
    No artificial launch deadline. ChiRi Studio is independently funded and releases are driven by technical readiness, validation and legal/commercial readiness rather than a forced public launch date.
    Where HQ-Lite can fit

    Local defensive capability without enterprise-scale complexity.

    HQ-Lite is intended for smaller organisations and edge environments that need stronger local visibility and controlled defensive capability without the footprint of an enterprise SOC platform.

    SMEs

    Local defensive visibility without building a full internal SOC.

    MSPs

    A repeatable edge-appliance model for managed customer environments.

    Hospitality

    Guest Wi-Fi, IoT, back-office and uptime-sensitive environments.

    Education & community organisations

    Practical low-power local visibility for constrained environments.

    Branch sites

    Edge decision-making close to remote users and devices.

    Hosting / VPS edge

    Traffic pressure, abuse visibility and controlled mitigation paths.

    FAQ

    Plain-English answers to the questions we expect people to ask.

    What is HQ-Lite?

    HQ-Lite is a local-first defensive edge appliance that sits inline between WAN and LAN. It combines network services, edge visibility, device context, Guardian and controlled defensive functions in one local system.

    Is HQ-Lite just a router or firewall?

    No. It includes routing and firewall functions, but the wider system also provides network visibility, device context, defensive event handling, system-health monitoring and Guardian's bounded decision process.

    Does HQ-Lite require endpoint agents?

    No endpoint agents are required for core edge visibility. HQ-Lite works from its position in the network.

    Does HQ-Lite require a public cloud dashboard?

    No. Core management is local and the operator dashboard remains LAN-only. Future verification services are designed as controlled supporting services, not as a public SaaS control plane for the customer network.

    Can HQ-Lite operate if the verification service is unavailable?

    The core local appliance is designed to remain operational at the edge. External verification should improve intelligence quality, not turn the local network into a cloud-dependent system.

    Does HQ-Lite read my passwords, private messages or banking information?

    HQ-Lite is not designed to collect or export passwords, login credentials, authentication tokens, session secrets, private message/email contents, banking credentials or payment-card details. Its defensive model is based on network and security context rather than collecting private application content.

    Does HQ-Lite perform TLS interception?

    TLS interception is not a normal requirement of the HQ-Lite core operating model.

    What is Guardian?

    Guardian is HQ-Lite's bounded local decision and response engine. It observes relevant activity, uses local context and verified intelligence, assesses risk, explains decisions and coordinates controlled action when policy permits.

    Is Guardian an AI chatbot?

    No. Guardian is not an LLM, chatbot or prompt-driven generative AI assistant. ChiRi Studio uses Digital Brain as an architectural term for its bounded observation, context, assessment, decision and response process.

    What is an IOC?

    An Indicator of Compromise is a security indicator such as an IP, domain or URL that can contribute to a defensive decision. HQ-Lite distinguishes observations and candidates from stronger verified intelligence.

    What is Blackhole?

    Blackhole is HQ-Lite’s dynamic containment layer within the firewall path. Approved hostile-source entries are maintained through the local firewall policy and synchronised with the XDP/eBPF edge blocking map, allowing matching traffic to be dropped earlier at the network edge. When an entry expires or is removed, the corresponding edge block is removed as well.

    What is a Threat Candidate Event?

    A Threat Candidate Event is a security-relevant observation that may deserve verification. It may be a suspicious URL, domain, DNS observation or scanning source. A candidate is not automatic proof of malicious intent.

    What are Watchdog, Echo-Probe and Noctilux?

    Watchdog monitors the integrity and operational state of the appliance. Echo-Probe provides local network identity and device context. Noctilux provides system-health visibility including resources, storage activity, temperatures and process information.

    Does ChiRi Studio see my entire network?

    Core management remains local. Planned external communication is purpose-limited: minimal service health/heartbeat information and sanitised security candidates for verification rather than a copy of the customer's full network activity.

    Does HQ-Lite block every TOR connection or every country on a list?

    No. Region, ASN and TOR information are context. They are not automatic proof of malicious intent and should only influence action through explicit policy and evidence.

    Can HQ-Lite stop every cyberattack?

    No security appliance can guarantee that. HQ-Lite is designed to improve local visibility, context, verified intelligence and controlled defensive response.

    About ChiRi Studio

    Founder-led, UK-based and developing our own defensive edge technology.

    ChiRi Studio Ltd is building and validating its own local-first defensive edge technology. The company is focused on product development, operational trust and practical deployment rather than general-purpose IT services.

    Piotr Danielewicz — Co-founder & CTO

    Security, networking, Linux systems, architecture, Guardian, edge infrastructure and live technical validation.

    Kinga Danielewicz — Co-founder & CEO

    Product vision, UI/UX, design direction, operations, communication and product clarity.

    Contact

    Technical and strategic conversations welcome.

    HQ-Lite remains in technical validation. We are open to conversations with UK technology operators, MSPs and organisations interested in the direction of local-first defensive edge security and future controlled validation.

    If a public channel is not linked from chiristudio.com, it should not be treated as an official ChiRi Studio channel.