Telosforge
ATLAS

For your technical and risk teams.

How ATLAS is built, how it stays inside your perimeter, and how adoption is governed and measured.

Talk to usExplore ATLAS
Technology

Architecture, security and supported technologies.

Thin clients, one service backbone, one knowledge foundation. The knowledge is the product. Everything else is a view.

20,000+lines held in a single pass
Architecture at a glance

Clients: a web app for business, compliance and knowledge engineers, plus an IDE plugin for developers. No business logic in clients.

Services: one REST backbone for ingestion, meaning detection, mapping, documentation, specification and reconciliation. All AI flows through one controlled gateway.

Knowledge foundation: a structure store (graph of your code) and a meaning store (ontology of business knowledge), permanently linked by stable identifiers. Ask from business to line of code, or from code to regulation.

Security and deployment
  • Deploys into your own cloud tenant. Your identity, network and monitoring apply unchanged.
  • Code, knowledge and generated artifacts stay yours, in your environment.
  • You choose the models. Usage is logged. No model is the final authority.
  • Open foundations and open standards. No proprietary lock-in.

ATLAS is designed to run inside the trust boundaries you already govern.

Assets ATLAS ingests
Source codeDocumentsConfig dataSystem logs and metricsTrouble tickets

Code says what the system does. The assets around it say why, how it behaves in production and where it hurts.

Supported technologies

Code: COBOL, JCL, PL/I, REXX, Java, C, C++, VB, C#

Integration and data: CICS, IMS, MQ, Kafka, SOAP, REST, SQL, Domino

Documents: Office, OpenOffice, PDF, Markdown, Mermaid

Signals and config: logs, metrics, ticket exports, JSON, YAML, XML, CSV. New readers plug in per engagement.

A model tailored to each client

Built on Telosforge's own knowledge of legacy code (PL/I idioms, JCL flows, CICS patterns) and tailored to each client's estate. Self-hosted inside your perimeter. Route each task to the tailored model, your hyperscaler's models, or both. Quality and cost are measured per client, with a method agreed in advance.

Core-banking knowledge packs
CoreLanguageCovered by the pack
AlnovaCOBOL100%
HoganCOBOL90%+
FIS SystematicsCOBOL90%+
FIS IBSCOBOL90%+
Fiserv SignatureCOBOL90%+
Temenos Transact T24Java90%+

Coverage is the share of each platform the pack already maps. Packs separate vanilla product from your customizations: exactly where your risk, value and effort hide.

Knowledge model

Your business vocabulary, written down so software can check it.

Most of the knowledge base is pre-built and reusable. Only what makes you unique needs mapping.

You own it

Knowledge becomes a company asset, not a person's.

Machines verify it

Contradictions surface as findings, not incidents.

Regulators get evidence

Audit answers become queries, not archaeology.

AI gets guardrails

Answers grounded in your verified vocabulary.

BIAN

Banking processes and capabilities

The industry map of what a bank does and how capabilities connect.

FIBO

Financial concepts and contracts

Parties, products, contracts, obligations. Shared, unambiguous meaning.

ACORD

Insurance vocabulary and data

Policies, claims, parties and exchanges across carriers and brokers.

A head start, a mirror, never a straitjacket. Where reality differs from the standard, the code is the final arbiter.
Adoption details

Principles, KPIs and who does what.

Evidence by design

Every claim traces back to the code.

Ownership by design

Every domain has a named owner.

Security by design

Least privilege by default, per domain and role.

Human control

No machine judgment ships alone.

Knowledge as a product

Versioned, governed, owned. It never decays.