INTERNAL TOMORIS PLATFORM
Development & operations platform.
WERFT is the internal control center for TOMORIS and GRID in-house developments: inventory, delivery and operating status of every instance, servers, runners and agents, backed by evidence instead of assumptions.
IN BRIEF
What is Werft?
WERFT is the technical foundation behind TOMORIS product development. The platform reconciles what should be running according to the registry with what the servers themselves report, and triggers project creation, rollout and cleanup only via narrowly approved workflows.
- THE TASK
What problem does Werft solve?
As the number of products grows, repositories, operating states, credentials, agents and delivery evidence become scattered. Without shared control, blind spots and inconsistent approvals emerge.
- AVAILABILITY
INTERNAL TOMORIS PLATFORM
Protected work and control platform exclusively for approved TOMORIS roles; not publicly available.
- THE ROLE OF AIAI
What the AI does
In the SEO tool, an AI drafts suggestions for titles and descriptions; crawling and findings also run without it. States and colors in WERFT come from evidence, never from a language model.
Internal TOMORIS platform
Your next step.
Agreed in concrete terms.
- Capture your software task and existing systems
- Plan verifiable work packages, approvals and handover
- Clarify suitable implementation and operational responsibility
What you request is a software project with TOMORIS. The internal WERFT platform itself is not offered as a publicly available license.
FEATURES & MODULES
What the solution
delivers day to day.
- 01
Target and actual
The registry says what should run; the servers report what is running. The deviation is the finding. A value without evidence turns gray, never green.
- 02
Rollout with proof of effect
A rollout only counts as done when the service itself reports the deployed version. Every number carries where it comes from and when it was collected.
- 03
Projects from templates
New projects are created from vetted templates in a guided workflow, with permissions and the four-eyes principle for requests without an administrator role.
- 04
Tools & agents
CodeSentry, CodeReviewer, IdeaGenerator and the SEO optimizer are triggered from WERFT, which shows the result and the cost. The background agents of the fleet appear in the same view.
IN OPERATION
How Werft
fits into everyday work.
- 01
Maintain the inventory
Projects, instances, servers and runners are listed in the registry with their target location; changes to it go through pull requests.
- 02
Receive the status
Every server reports its version, health and delivery status itself. WERFT does not measure; it shows what is evidenced.
- 03
Change in a controlled way
Creating, rolling out, renaming and removing run only via approved GitHub workflows; otherwise the write path stays closed.
WHO IS IT FOR?
For people who need clarity.
- TOMORIS development and platform operations
- Owners of internal software and GRID services
- Approved roles for requests, review and administration
RESULT
What Werft improves in concrete terms.
- 01One shared control point for in-house developments
- 02Traceable quality and approval gates
- 03Less operational blindness across the product portfolio
ENVIRONMENT & INTEGRATIONS
Close to the process
instead of isolated.
- GitHub repositories and workflows
- TOMORIS Registry
- Self-reporting by the servers
- CodeSentry, CodeReviewer and IdeaGenerator
SUMMARY
Werft at a glance
- What is it?
- WERFT is the technical foundation behind TOMORIS product development. The platform reconciles what should be running according to the registry with what the servers themselves report, and triggers project creation, rollout and cleanup only via narrowly approved workflows.
- Who is it for?
- TOMORIS development and platform operations; Owners of internal software and GRID services; Approved roles for requests, review and administration.
- What does it deliver?
- One shared control point for in-house developments; Traceable quality and approval gates; Less operational blindness across the product portfolio.
- How is it available?
- INTERNAL TOMORIS PLATFORM — Protected work and control platform exclusively for approved TOMORIS roles; not publicly available.
CLEAR ANSWERS
Frequently asked
questions.
Is WERFT a public developer portal?
No. WERFT is a protected internal platform for approved TOMORIS roles.
Does WERFT replace GitHub?
No. GitHub remains the repository and pull request system; WERFT connects the operational delivery and operations path around it.
Does WERFT develop software on its own?
No. An autonomous job path planned earlier has been removed. WERFT shows states and triggers approved workflows; code changes go through pull requests with mandatory checks.
YOUR NEXT STEP
Find the right fit
for Werft.
We clarify the goal, environment, integrations and the permissible next step.