FAQ
Questions about Telikos, answered plainly.
What it reads, how it cites, what it will not do, and where it runs. For the detail, see how it works and security.
What Telikos is
What is Telikos?
Telikos is a read-only appliance that reads a legacy estate's COBOL, JCL and procedures, copybooks, DB2 SQL and CICS definitions, builds a graph of facts about how it all fits together, and answers questions in plain language. Every statement in an answer cites the exact source lines behind it. It runs inside your network and is designed, built and supported by Nisius.
Which languages and artifacts does Telikos read?
Telikos reads COBOL programs, copybooks, JCL and procedures, DB2 SQL and DDL, and CICS definitions. From them it records programs, paragraphs, data items, files and the datasets bound to them, jobs and steps, tables and columns, CICS transactions, maps and queues, and the IF and EVALUATE statements that route data.
What kinds of questions can Telikos answer?
Telikos answers questions about how the estate works: which jobs run a program, what reads a dataset a job writes, which program decides an outcome, where a field is set, and what would be affected if you changed a program. Each answer cites the program line, job step or table definition it came from.
Does Telikos translate COBOL into Java or another language?
No. Telikos does not rewrite code. It explains what you have, with evidence, so your team can maintain it, change it safely or plan a modernization from facts instead of guesses.
Who builds Telikos?
Telikos is designed, built and supported by Nisius.
Accuracy and citations
How does Telikos avoid making things up?
Telikos composes answers only from evidence it retrieved, and every statement must cite that evidence. A validator checks each citation and drops any statement that fails; a dropped statement is never shown as a fact. Deterministic parsers read the code first, and a language model, if one is used, sees only a bounded part of the graph and the source lines it points to, never the raw estate.
Does Telikos need a language model?
No. Answers can be composed with no model at all, from the facts the parsers recorded. A local model running on the appliance is optional; it can write summaries and business rules, which go to your experts' review queue as pending.
What happens when Telikos is wrong?
Your experts confirm, reject or correct the fact. A confirmation sets its confidence to 1.00, a rejected fact disappears from every answer and map but is kept for the audit trail, and a correction is stored beside the original and is not overwritten when the code is ingested again.
What does Telikos do with things it cannot resolve?
Telikos records them as unknowns instead of guessing: a call whose target is decided at run time, a missing copybook, a dataset nobody writes. The list is ranked by how central the affected part of the estate is and says which artifacts would close each gap.
What do the confidence scores mean?
Each fact's confidence says how it was established: 0.95 for a structural fact from a parser, 0.90 for a link the resolver matched uniquely, 0.60 or 0.30 for heuristic or ambiguous matches (which also record an unknown), at most 0.80 for model output, and 1.00 only when one of your experts confirms or corrects it.
Security and deployment
Is Telikos SaaS?
No. Telikos is a self-hosted appliance that runs with Docker Compose on a host you provide, inside your network. All processing and storage stay inside your boundary.
Does any of our source code leave our network?
No. The appliance's services sit on a network with no route out, there is no telemetry or phone-home, and model endpoints outside the local network are refused unless an administrator explicitly allows them, which the appliance configuration does not.
Does Telikos write to our systems or need production data?
No. Connectors only read, and Git copies have their remote removed. Telikos reads source artifacts only and needs no production business data.
Can Telikos run air-gapped?
Yes. The appliance runs without outbound access, and language models can be exported and imported from a file with sha256 checks.
Is our code used to train AI models?
No. Telikos does not train models. If a local model is used, it receives bounded excerpts at inference time only, on the appliance.
Pilot and pricing
How do we start with Telikos?
With a three-week pilot on one flow you choose, such as nightly claims adjudication or month-end close. Week one installs the appliance and ingests the flow, week two is a joint review with your experts, and in week three your team asks its real questions and grades the cited answers.
What do we need to provide for a pilot?
The source for the flow (COBOL, copybooks, JCL and procedures, DB2 DDL, and CICS definitions if the flow is online), read-only access to it, a host with 8 vCPU, 32 GB of memory and 100 GB of disk running Docker, and a few people: a pilot lead, an infrastructure contact, a security reviewer and two to four subject-matter experts for short sessions.
How much does Telikos cost?
The pilot is a fixed fee set by the size of the flow and credited in full toward a subscription, and subscription pricing is scoped with you after the pilot. We quote in conversation, not on a page: contact us and we will tell you plainly.
Ask us yours
If your question is not here, ask us. We answer in writing, and plainly.