Attera GmbHEnterprise software engineeringVienna · EU

Software for the next era of the enterprise.

fig. 00 - the core θ 000° · φ 000°

We design and build the systems large organisations will run on for the next decade: agentic, composable, zero-trust by default. We make agentic value accessible to the enterprise, securely. Engineered, not assembled.

Start a conversation → Reference architecture ↓
Method
Context engineering · Agent harness
Core
Composable · contract-first
Trust
Zero-trust · EU-resident
Status
Accepting Q1 2027
UTC
--:--:--
§01

Enterprise software is being rewritten by three forces.

Each one changes what an engineering organisation is for.

  1. 01

    Agentic delivery

    Code is no longer the bottleneck. Verification is. We run engineering as a loop of specification, autonomous generation and formal review, with engineered context and a hardened harness around every agent. Humans own intent and architecture; agents own throughput.

    spec-driven / eval-gated / auditable
  2. 02

    Composable core

    Monoliths and twelve-year-old ERP customisations give way to bounded, event-driven domains behind stable contracts. Every capability is a service with an owner, an SLO and a version.

    domain-driven / contract-first / event-sourced
  3. 03

    Zero-trust by default

    Identity for every workload, not just every user. Signed artefacts, policy as code, encrypted everything, EU data residency. Compliance becomes a build output, not a quarterly audit.

    workload identity / policy-as-code / EU-resident
§02

Agentic value, made accessible to the enterprise.

Model capability is cheap. Two engineering disciplines turn it into systems your CISO signs off.

2.1

Context engineering

A model is only as good as what reaches it. We treat context as an engineered, versioned artefact: which documents, schemas, tools and memories enter the window, in what order, under whose access rights. Context is retrieved from governed sources, scoped per identity, measured for relevance and token cost, and tested like code.

DOCS · POLICIES ERP · SCHEMAS TOOL CONTRACTS MEMORY · TTL POLICY FILTERIDENTITY-SCOPEDLEAST PRIVILEGE CONTEXT WINDOWBUDGET 24K TOKRANKED · EVAL'D MODEL VERSIONED CONTEXT PACK · DIFFED · REVIEWED
  • Governed retrievalScoped by the caller's identity, never by the agent's
  • Contracts as contextSchemas and tool specs enter the window, not prose
  • Memory with policyRetention, residency and deletion per record
  • MeasuredRelevance evals and token budgets per task
  • VersionedContext packs are diffed and reviewed like code
2.2

Agent harness

Capability without a harness is a liability. The harness is the runtime that wraps every agent: durable execution, least-privilege tool permissions, policy checks before any side effect, eval gates before promotion, human approval where the stakes demand it, and a replayable trace of every decision. Agents run inside it, never beside it.

HARNESS · DURABLE RUNTIME PLAN ACT · TOOL VERIFY REPLAN IDENTITY POLICY EVALS TRACE HUMAN> 5K EUR PROD NO BYPASS
  • Durable runsResumable, idempotent, Temporal-backed
  • Least-privilege toolsEach tool call carries its own scoped credential
  • Policy before side effectsOPA decisions on every write, payment, send
  • Eval gatesNo promotion below threshold, canary by default
  • Replayable traceEvery decision in OpenTelemetry, kept for audit
§03

One reference architecture, instantiated per enterprise.

Open standards at every seam. No proprietary runtime. No lock-in.

ATTERA CORE · 5 PLANES · 2 RAILS OBSERVABILITY · OTEL · SLO IDENTITY · POLICY · AUDIT EXPERIENCEWeb · Mobile · Internal tools · Partner APIsReact · Swift · GraphQL AGENT & ORCHESTRATION PLANEContext packs · Agent harness · Policy · Human-in-the-loopTemporal · MCP · OPA DOMAIN SERVICESBounded contexts · Contract-first · Event-sourcedGo · Rust · gRPC DATA FABRICStreams · Lakehouse · Vector index · LineageKafka · Postgres · Iceberg ZERO-TRUST INFRASTRUCTUREWorkload identity · Signed supply chain · EU cloud / on-premK8s · SPIFFE · Sigstore
fig. 01 - reference architecturescale 1:1 · rev. 2026.10
attera.system.yamlvalidating…
Availability target
0
p95 latency budget
0
Signed artefacts
0
Proprietary runtimes
0
§04

What we build. End to end, or where it hurts most.

§05

From first call to production. Measured in weeks, not quarters.

  1. T−0

    Discover

    Two weeks inside your domain. We map systems, flows, risks and the one metric that matters. Output: a target architecture and a costed plan.

    2 weeks
  2. T+2w

    Architect

    Contracts, domain boundaries, threat model, context model, harness design, SLOs. Decision records for everything. A walking skeleton in production before design is "done".

    3–4 weeks
  3. T+6w

    Build

    Agent-accelerated delivery in weekly increments. Every change contract-tested, signed and deployed progressively. Working software every Friday.

    6–16 weeks
  4. T+∞

    Operate

    SLO-backed operations with named engineers. Error budgets drive the roadmap. The system compounds instead of decaying.

    ongoing
§06

Start the next era of your systems.

Tell us what your enterprise runs on today. We reply within one business day.

hello@attera.at
Entity
Attera GmbH
Location
Vienna · Austria · EU
Response
≤ 1 business day
Engagements
Discovery from 2 weeks