What AngusKit is: an AI-native software engineering platform, six products, one spine

AngusKit is an AI-native software engineering platform: six products, one spine. Work runs from agents to code, artifacts, testing, security, and insight, and covers a change from the draft through the review after release. AI drafts and checks. A named person confirms the merge into the main branch, the artifact publish, and the release before any of those take effect. Code indexes, model context, and artifact metadata stay in your cluster. Unauthorized credentials are not sent to a public model provider.

One install brings the sign-in portal, AngusGM, and six applications. The six applications share that identity. The database name is angus. Each application is still its own process and its own pages. How to use a given console is in that application's article, linked at the end.

The main problems it solves

From commit to release, the record is split. The ticket, the review, the artifact, and the test report each live in a different system. To see whether this merge passed, you open yet another site. On this spine those records hang on the same change, and the build, test, and security results sit next to the merge request.
The agent stays in a chat window beside the work. The code change, the test script, and the release policy have to be copied in before it can use them. Here the agent sits in front of that work, and the draft happens under the same sign-in. A draft becomes code on the main branch, an artifact in the repository, or a release that has gone out only after a person confirms it.
Every extra system means another round of accounts, permissions, audit, and upgrades. The person is created once in the portal. The six applications recognize that same person, and they share one permission model and one audit trail. You are not reconciling the same fact across several admin panels. A later upgrade maintains this one install directory. The six applications are version-locked in the package.

Note: It does not train models, and it does not fold the six applications into one menu. The package starts processes and a database. The programs AngusSecurity uses to run checks are not in this package. After install you still follow that product's install notes and put the engines where the security process can read them. If the portal is down, sign-in for all six stops, because the portal issues the token.

What it includes

The homepage title is "The AI-native software engineering platform". The line under the title is the order of the work: agents, code, artifacts, testing, security, insight. Under that are five stages: business analysis, AI drafting, human confirmation, intelligent analysis, and skills capture. Human confirmation is the stage where the line stops for a person.

Each application owns one stop on that line. The paragraphs below say where it connects. Buttons and click-paths stay in that product's own article.

AngusAI is "Agents". You build an agent in its pages and attach knowledge, tools, and guardrails. The model is one you already buy or host. Publish the agent as an application first, then try it from AI Chat or Enter chat. The suite does not train models.

AngusGit is "Code". Repositories and pipelines live here. A pipeline is YAML or a visual editor. Build, test, and security results return to the merge request, and a ticket can be linked to this change. On a protected branch, the merge button stays unavailable until the conditions are met.

AngusRepo is "Artifacts". Twenty-eight common formats are published, cached, and aggregated in one repository. mvn, npm, and docker keep their commands. You change the address. A version that failed tests or a security check stops before publish. A package that has not been scanned is not a pass.

AngusTester is "Testing". One YAML covers API, performance, Web, mobile, LLM, and security tests. When an assertion fails, the pipeline can see that this run did not pass, and the merge request can be matched to that execution. The run is on the node Agent. If the node is offline, the run does not start.

AngusSecurity is "Security". Code, secrets, dependencies, and images become one check. The result returns to merge and release, and the run leaves a report. Quality-tool findings stay in their own list and are not treated as the security verdict. An empty list while the check is still running is not a pass.

AngusInsight is "Insight". A browser SDK writes channels, funnels, paths, and frontend errors into a database you run. You read the traffic and the errors around this release in the console.

Sign-in happens on the portal, at gm.<your-domain>. The six processes ask the portal to check the token. Kit appears next to the products in the docs site so this suite manual has an entry.

Where it is used

The review, the artifact, and the test report for one commit sit in three systems, and you cannot tell which change they belong to. The code enters an AngusGit merge request. The pipeline writes the build and test results back onto that request. The artifact is found in AngusRepo by its coordinates. A person reads the result on the merge request and then decides whether to merge. The person in the portal can already open these three applications, so you do not create three accounts. The agent does not click merge.
Code and packages have to be copied to an outside host before anyone on the internal network can see them. Point the seven names at your own machine and keep the install on that machine. Code indexes, model context, and artifact metadata stay local. Unauthorized credentials are not sent to a public model provider. The browser opens your own gm.<domain>. An IP address or localhost stops the wizard. The copy to an outside host can stop there.
An agent drafted a change, a script, or a release policy, and the next step would merge it to the main branch. Drafting stays in AngusAI. Merge, publish, and release stop at human confirmation. That door is the third stage on the homepage. The English on the card is Human decision gate. Who confirms inside a given application is that application's own rule. The agent has to be published as an application before you can try it in chat. A chat that worked is not a merge to the main branch.
Tests, security, and traffic after release each have their own report, and the next round cannot tell whether the last round passed. Put the test report, the security report, and the traffic and errors from AngusInsight on either side of the same release. The fourth stage on the homepage is intelligent analysis. The English on the card is Return to facts. You judge whether the change did what you intended. The fifth stage, skills capture, stores prompts, flows, knowledge, and permission boundaries as a versioned specification for the next draft. A change in the numbers does not open the merge or release door by itself.

What is sharp about it

Commit to release is one line. The ticket, the review, the artifact, and the test report hang on the same change. You do not open another site to match the conclusion before merge.
The system and the data stay inside your boundary. The default install is Docker Compose. It can go into Kubernetes, and it can be installed from an offline package when the host cannot reach the public network. It can also be installed on a domestic operating system. Code indexes, model context, and artifact metadata stay in the local cluster. Health checks and upgrades use this one install directory.
Testing and security are the door before release. A change that did not pass stops before merge and publish, and it does not become a production artifact. A check that has not finished is not a pass. Quality-tool findings are not used as the security verdict.
Skills and APIs attach to the systems you already run. Each application provides an API and MCP. Internal pipeline steps and services can be kept as skills and reused when drafting. The suite has no single MCP address. The assistant uses the address and token of the application it enters.
People and permissions are governed once. The six applications share the portal's identity, permissions, and audit log. The portal can use the directory and single sign-on you already have, including LDAP and SAML. Disabling a person stops all six, because the portal issues the token. Actions leave an audit record.
The engineering definitions live in the repository. Each application has OpenAPI and declarative YAML. Pipelines, test scripts, and resource definitions stay in Git with a version. Moving to another environment does not mean editing them by hand again.

How you install it

The boundary has to be installed before any of those doors exist. The install manual has three paths. The default is Docker Compose. Without Docker, use the host ZIP. For a cluster, use Kubernetes. Only the default path is walked here. The other two pages are linked at the end.

Production is Linux x86_64. docker compose version must print a version. macOS is fine for a trial. Run the wizard as the user you are logged in as. Do not prefix it with sudo. Docker Desktop cannot mount a directory root created. To use /opt/angus, change the owner to the current user first.

All seven names must resolve to this machine: gm, ai, git, repo, tester, insight, security. Port 80 must be free. Port 443 must be free if you will use HTTPS. Git SSH is 2222. The Tester execution node is 7100. Ports 8801 through 8809 belong to the applications. The proxy forwards them. Do not treat those ports as the browser entry. Do not publish 9528 on the public network.

Download the package from the public raw repository on https://repo.anguskit.com. The file name is the one listed on the install page. The unpacked directory is AngusKit-1.0.0.

unzip <package-file>.zip cd AngusKit-1.0.0 ./install.sh

On Windows, run install.bat. Start, stop, check, and upgrade with angusctl in this directory: render, start, stop, status, doctor, and upgrade.

The wizard prompts are in English.

On screen	What you enter	What it decides
`Install mode`	Press Enter	Docker Compose. Enter keeps the default
`Access`	Type `2`	The bundled reverse proxy and subdomains. Enter stays on option 1, which is access by port and does not match `gm.<domain>`
Reverse proxy	Press Enter	Caddy. Let's Encrypt can be configured only with Caddy
Certificate	Type a number. There is no default	`1` is your PEM, `2` is a self-signed certificate from the package, `3` is Let's Encrypt, `4` is HTTP only. Leaving it blank stops the wizard
Database	Press Enter	Compose starts MySQL 8 on this machine
Install directory	Press Enter	The current directory, which becomes `$ANGUS_HOME`
Apex domain	Type an apex such as `example.com`	Builds the seven names. `gm.example.com` adds an extra `gm.`

The administrator password must be at least 8 characters. Write it down outside the wizard. Do not keep the public default database password the wizard offers. The data directory takes that password only the first time it is created. After that, changing angus.env or docker/.env without changing the password already stored in the database makes the applications fail to connect. The install page has the change procedure. The default string is not repeated here.

Certificates 1, 2, or 3 open https://gm.<your-domain>/. Certificate 4 opens http://gm.<your-domain>/. A self-signed certificate makes the browser warn. That is the certificate type, not a portal that failed to start.

If docker compose is missing, the wizard prints ERROR: docker compose not found. Use the host ZIP page. Kubernetes uses the chart's switches. Those steps are on the cluster page.

MCP

Each application provides its own MCP, so an editor assistant can reach repositories, pipelines, artifacts, tests, and security checks. The suite has no single MCP URL. The assistant uses the address and token variable from the application it should enter. The portal signs the user access token. It does not replace that application's /mcp.

The homepage says each product can connect context to a host such as Cursor, Claude, or Qoder. Questions stay in the editor. Whether a change can merge or publish is still a fact in that application, and a person still confirms it. Do not commit the token or paste it into chat. Prefixes differ. Use the variable named in that product's article. A token from one product does not authenticate another.

SDK

There is no SDK named AngusKit. Where an application ships a REST SDK, it is in that application's API reference, called with a Bearer token. You still push code with a Git client and still publish with mvn, npm, or docker. Installing the suite does not replace those commands.

Each application has OpenAPI and declarative YAML. Those are that application's own API and resource definitions. Pipelines and test scripts go into the repository from that definition. Call the API reference of the application you are talking to.

FAQ

Is AngusKit an eighth console?

No. It is the package that installs the portal and six applications. Each application stays its own process and its own pages. Kit is in the docs so the suite manual has an entry.

Where do I sign in?

At gm.<your-domain>. Do not use localhost:8801 as the real entry. The redirect will not match the domain. HTTPS or HTTP follows the certificate number you typed.

Can I install without Docker?

Yes. When the wizard prints ERROR: docker compose not found, use the host ZIP. A cluster uses the Kubernetes page. Compose is only the default path.

Do the six applications start together?

They start in order. MySQL and GM come first, then AI, Git, Repo, Tester, and Insight. Security is last among the applications, and the reverse proxy comes after that. angusctl waits until the previous one is ready. After doctor: OK and Install finished., wait about a minute, then run ./bin/angusctl.sh status.

The site will not open. Do I reinstall?

Look for Install finished. first. If it is missing, read the last lines of $ANGUS_HOME/logs/install.log. If port 80 is taken by another Nginx, Caddy, or IIS, stop that and run the wizard again. Communications link failure in the log means the database host inside the container must not be 127.0.0.1. Use mysql or postgres, then render and start.

Is there one MCP or one SDK for the suite?

No. Addresses and SDKs belong to each application. The suite gives you one sign-in, one permission model, and one install directory.