Release and dependency management
Who depends on whom — and what ships where, and when?
aktivities.ai answers both questions in one picture: your applications, environments and infrastructure as a dependency graph, every planned release on a shared timeline. You see collisions before they happen.
Early access · Design-partner phase · Hosted in Germany
released planned collision dependency
Illustrative view: four releases across two calendar weeks. Shipping payments-api pulls order-service and customer-portal along with it; SAP transport TR-4711 hits the same production environment on Thursday as customer-portal — the collision is flagged.
Where teams start
The release plan lives in three places. None of them is current.
Not because nobody maintains it, but because dates, dependencies and sign-offs sit in separate tools. Someone connects them from memory — usually once something has already gone wrong.
-
XLSX
The calendar is a spreadsheet
Whoever saved last is right. Whoever has never seen the file plans against it.
-
WIKI
The dependencies live in the wiki
Written for the last audit, unverified since. What a release drags with it is known only to people who have been around long enough.
-
MAIL
The sign-off came by email
Six months later, nobody can show who put what into which environment, and when.
Dependency graph
See what a release drags with it
Applications, environments and infrastructure are not three lists — they are one network. aktivities.ai keeps that network current and answers the question that precedes every change: what hangs off this?
- Impact analysis both ways. Forwards: what does this change touch? Backwards: what does this application depend on?
- One model for every layer. Applications, environments, hosts, databases and SAP clients in the same graph.
- Facts instead of guesses. Which version is running in which environment — and since when.
4 objects in the blast radius of this release
Release calendar
One calendar for every team — and every environment
Every planned deployment, every maintenance window, every transport on one timeline. Two releases in the same window on the same environment stop being a surprise and become a flagged entry.
- Collisions are flagged, not explained afterwards — including freeze periods and maintenance windows.
- Filter by team, environment, application or period. Every role sees its own slice in the context of all the others.
- Wired to the graph. A date knows its application, and the application knows its dependencies.
done planned collision freeze
Thu 13 Aug customer-portal v11.0 and SAP transport TR-4711 hit the same production environment.
What else belongs here
The things your auditors ask about
Complete audit trail
Every change is versioned: who, when, what, before and after. Answers for audit and internal control without the follow-up work.
Roles, permissions, SSO
A fine-grained permission model with sign-in via Keycloak, LDAP or SAML. Permissions follow your organisation, not the other way round.
German, English, Ukrainian
The interface speaks three languages — for distributed teams, external suppliers and nearshore partners.
AI access over MCP
An MCP server makes your release landscape queryable by AI agents. Ask in plain language what Friday's release touches.
Hosted in Germany
Operated in German and EU data centres, processed under the GDPR. No transfers to third countries.
A separate database per customer
Every customer instance runs physically apart on its own database. No shared tables, no tenant column as the only boundary.
From practice
Three questions that get asked on Mondays
Configuration
“Why does it work on ACC but not on PROD?”
Configuration values are held and versioned per environment. Comparing two environments is a view — not an afternoon of digging.
Drift becomes visible before it becomes an incident.
SAP
“When does the transport reach which client?”
aktivities.ai models SAP landscapes with their clients and transport requests as first-class objects — in the same calendar and the same graph as everything else.
Transports and application releases in one plan.
Audit
“Who signed this off back in March?”
Sign-offs, changes and ownership are recorded without gaps. The answer is a query — not a reconstruction from old mailboxes.
Evidence without a week of preparation.
One price per landscape. Not per head.
We count objects in your catalogue — applications, environments, hosts, SAP systems. Everything else is unlimited: users, entries, releases, API and AI queries. A release plan only works when everyone may record, see and query everything — there is no usage meter here.
Team
€290 / month
Up to 500 objects · unlimited users
Example: 35 applications, 6 environments, 120 servers and databases, 2 SAP systems — 163 objects, not even half full.
For one team that wants its release plan out of the spreadsheet.
- Unlimited users
- Dependency graph and release calendar
- Audit trail
Business
€890 / month
Up to 2,500 objects · unlimited users
Example: 150 applications, 25 environments, 1,200 servers and databases, 15 SAP systems — 1,390 objects, room to grow.
For several teams that can get in each other's way.
- SSO via SAML and OIDC
- Reports and analytics
- API and MCP access, unlimited
- Priority support
Enterprise
On request
Unlimited objects · unlimited users
When nobody knows the count by heart any more — which is exactly why there is no counter.
For landscapes where how it runs is part of the requirement.
- Dedicated cluster
- LDAP integration
- On-premises deployment available
- Data processing agreement and bespoke contracts
Which band fits? Count along.
Four numbers off the top of your head are enough — to the nearest ten is fine. We count what carries a name; releases and values never count.
163 objects — Team, the band is 33% full
What does that mean per head?
The Business plan (a flat €890), spread across your team — compared with a per-seat tool at the market anchor of €60 per user.
Anchor: €55–70 per user/month is typical for per-seat portals (as of 08/2026). From about 15 people the flat price wins — and nobody has to debate who is “worth a seat”.
What counts as an object?
Everything in your catalogue that carries a name: an application, an environment, a host, a database, an SAP system. Releases, configuration values, approvals and history are not counted — working with the objects is always unlimited, otherwise the plan would grow gaps.
A worked example: 35 applications + 6 environments (INT, ACC, PROD, …) + 120 servers and databases + 2 SAP systems = 163 objects. An environment counts once — not once per application.
What does the AI integration cost?
Nothing extra, and there is no meter. The MCP server answers your AI agents’ questions (“what does Friday’s release touch?”) straight from your instance — these are ordinary API calls. The language model runs with your provider on your terms; we do not bill for what we do not pay for. Included from Business.
What happens when we outgrow the limit?
Nothing abrupt. You see where you stand, we get in touch, you switch plans — nothing gets switched off or deleted in the middle of a release.
Why not per user?
Because collisions get noticed where many eyes are on the same plan. Per-seat pricing raises exactly the question that makes a release calendar worthless: “does she really need an account?”
All prices exclude VAT and are billed annually — our current assumption, not a final price list: the terms are set together with our design partners, and whoever joins now keeps their price beyond the introductory phase.
Early access
Become a design partner
aktivities.ai is in its design-partner phase. We are taking on a limited number of companies to work through their release landscape with us.
-
An instance of your own
With your applications and environments, not a shared demo tenant.
-
A direct line
You talk to the people building the product. Requirements land on the roadmap or get a reasoned no.
-
Fixed terms
The early-access price holds beyond the introductory phase.