Connect GitHub and get a model in one sitting

Entelim reads your repositories and proposes the applications, their parts, who owns them and what depends on what. You approve what it found, and every fact in the model links back to the repository, file and commit it came from. When a model already lives in a file, import it beside what GitHub finds.

From sign-up to your first answer

  1. Sign up free. A CTO or VP of Engineering can start on the Community plan with no sales call first.
  2. Connect GitHub. On the "Bring in your company" step, enter your GitHub organisation and a read-only token. The token is stored encrypted for your organisation and never shown again. Connect Jira the same way if your backlog is where your systems are described.
  3. Carry on while Entelim reads. The import runs in the background, so nothing waits on it. Each repository that is a deployable application becomes a proposal, with its parts, its owners from the code-owners file and the dependencies the code states.
  4. Approve what it found. Nothing enters the model until a person approves it. The review page lists the applications, parts and links GitHub showed, each with why it was proposed and the file it was read from. Choose Approve all, or skip the ones that stay out of the model.
  5. Ask in the AI chat. Ask what breaks if a service fails. Every connection in the answer shows the repository, the file and the commit it was read from, with a link to the file on GitHub.

What else connects

  • Jira. Connect it at sign-up and Entelim reads your issues into the model.
  • ServiceNow. Pull your application list from the configuration database with one click; see how to stop typing every system in by hand.
  • Your own AI assistant. Connect the assistant your team already uses, read only and scoped to your organisation, on every plan. See Connect your AI assistant.
  • Files. Import Archi, Open Exchange and spreadsheet files when the model already exists. See import an existing model.

AI assistants

File imports