Skip to content
Let`s talk

PLATFORM

EpicStaff — the agent operating layer.

EpicStaff is an agent harness: the runtime layer in which your agents run, on your own infrastructure.

EpicStaff connects out only to the providers you configure keys for. Tools do what you tell them: a tool you build or enable that reaches the internet is your choice and your configuration.

Agent runtime, knowledge base, and audit layer. Runs on top of any LLM you run, inside your own infrastructure. Source-available. Deployed on-prem. Operating entirely within your air-gap.

See the Architecture

CAPABILITIES

Five things, all in today's release.

  • 01 · ORCHESTRATION

    Agent orchestration with files

    agents read and write files as first-class artefacts. one agent's output is another's input. routing is a primitive.

    • .txt
    • .pdf
    • .md
    • .json
    • .csv
    • office
    • s3-compat

  • 02 · GRAPH RAG

    Graph RAG over your documents

    paragraph-level retrieval + citation out of the box. graph layer extracts entities & relations so agents can follow connections across sources for multi-hop questions.

    tuning surface (extraction model, entity types, co-ref merging) exposed in config.

  • 03 · INTROSPECTION

    Introspective flow pattern

    "What do you do? How do you work? What do you need from me? What would you refuse to do?"

    the flow IS its own current documentation. onboarding a new colleague — not reading YAML.

  • 04 · IDENTITY · RBAC

    Identity, orgs & audit-scoped principals

    every audit entry attributable to a named principal. RBAC enforced at the platform layer across agents, flows, KBs, tools, audit slices.

  • 05 · AUDIT TRAIL

    Audit trail

    per-request logging. prompt text, tool calls with args, model response, agent identity, principal. stored in PostgreSQL, exportable as JSON / CSV. retention configurable.

    no PII stripped. the audit is the ground truth.

ARCHITECTURE

One outbound boundary. Everything else is internal.

Runs on top of any LLM you run, inside your own infrastructure.

  • Model adapter — the only outbound boundary

    swapping LLM is configuration, not code.

  • KB, audit, RBAC — internal

    they survive any LLM change. agents keep their definitions; audit keeps its history; RBAC keeps its scopes.

  • UI is optional

    everything is REST-addressable. embed inside your own dashboards or portal.

  • Epicflow integration is optional

    EpicStaff is fully usable standalone.

HOW IT FITS

Stays out of the way of what you already run.

  • LLM

    swapping LLM is configuration, not code.

  • N×

    multi-model: route between models — different agents, different models, same audit trail.

  • PM

    project management stays where it is. agents-as-resources via Epicflow if you want it.

  • IdP

    Role-based access control is built in. Connect your own identity provider — LDAP, OIDC, or SAML — for Enterprise and Defence deployments, available on request as part of a contract.

HOW TO EVALUATE

Deployed on-prem. Your infra, your code, your audit trail.

A guided onboarding walks your team through agent-definition patterns, KB setup, the introspection surface, RBAC and audit-trail review.

Let’s talk See the Architecture