Zum Hauptinhalt springen

Environments

πŸ€– Generated with Claude Code

βœ… Reviewed by Martin Riemann, 2026-09-02

Co-Authored-By: Claude (noreply@anthropic.com)

The company separates Development, (Fach)test and Prod everywhere. What an environment is, however, differs by product β€” which is why this page has three sections instead of one table:

  • TOGETHER runs on our own on-premises servers, in three named environments.
  • CCA has no shared environment set at all. Most of it runs on the customer's system.
  • Azure separates environments by subscription, for both product groups.

FACHTEST, STAGE and PROD are Together environments. They are not platform-wide names, and nothing in CCA corresponds to them.

Contents​

DocumentDescription
together-on-premises.mdThe three Together environments: server roles, the environment variables on every server, what differs between them
stage-decommissioning.mdSTAGE: the decision, what has to happen first, and the scale of the cleanup
vudev-decommissioning.mdVUDEV: what was removed, and the cleanup still open across the repositories

TOGETHER β€” On-Premises​

DEVELOPMENT is not a server environment: it is the developer's own machine. The other three are sets of on-premises servers, each a self-contained copy of the same shape β€” the same server roles, the same host names, its own domain controllers.

EnvironmentASPNETCORE_ENVIRONMENTHostActive
DevelopmentDevelopmentthe developer's machineβœ…
FachtestFachtestfachtest.servicebytogether.atβœ…
StageStagestage.servicebytogether.atβœ…
ProdProdwww.servicebytogether.atβœ…

Server roles, the variables every server carries and what actually differs between the three: together-on-premises.md.

STAGE is to be decommissioned. The decision is made, but nothing has been removed and the timing depends on three partner insurers rather than on us β€” see stage-decommissioning.md.

CCA​

CCA has no shared environment set, because the deployment model differs per product. For most customers, their installation is the environment.

There are two applications, each with a hosted counterpart: CCA9 is a Windows Forms desktop application, CCAOnline a web application, and both normally run on a server the customer provides. CCA Host-It is a CCA9 instance we host; CCA Cloud Edition is a CCAOnline instance we host.

ProductWhat it isRuns onThe environment is
CCA9Windows Forms desktop applicationa server the customer providesthat customer's installation
CCAOnlineweb applicationa server the customer providesthat customer's installation
CCA Host-Ita CCA9 instance we hostour Azure hostingour Azure hosting
CCA Cloud Edition (CloudEdi)a CCAOnline instance we hostour Azure hostingour Azure hosting
EndcustomerPortal (Kundenportal)broker self-service platformsplitboth β€” SPA and BFF in our Azure, EndcustomerApi inside the customer's CCAOnline

Two consequences are worth stating outright, because they have no equivalent on the Together side:

  • A CCA9 or CCAOnline environment includes a Microsoft subscription we do not own. The customer's documents live in their own SharePoint and are reached over the Graph API, so the environment boundary crosses into a foreign tenant. Documented for the hosted products in CCA-Hosting architecture β€” it holds for on-premises installations too.
  • There is no single "CCA production". CCA9 is installed at the customer, so several versions are in productive use across the customer base at any time. See git/ for what that means for branching.

The EndcustomerPortal is a self-service platform our customers β€” insurance brokers β€” offer to their customers, the people who bought the policies. It is the one CCA product that spans both sides of the boundary.

Development, test and production separation for CCA happens inside the hosted components and in Azure, below.

ProductDocumentation
CCA9products/cca/cca9/
CCAOnlineproducts/cca/ccaonline/
Cloud Edition, Host-Itproducts/cca/cca-hosting/
EndcustomerPortalproducts/cca/kundenportal/

Naming: the brand guide calls it CCA CloudEdi, the product pages CCA-Cloud Edition. Same product.

Azure​

In Azure the subscription is the environment boundary. There is no per-environment resource-group convention doing that job.

SubscriptionHoldsNote
Together-FachtestDevelopment, Fachtest, Stageall three non-production Key Vaults
Together-ProdProdalso holds the CCA-Hosting resources
TOGETHER CCA(historical)still active, but takes no new resources

A subscription name is not a scope signal. Together-Prod and Together-Fachtest hold Together and CCA resources. The CCA-Hosting environment (TIS-PROD-CCA_Weblight-AppGw, CCA-Hosting-SQL01, CCA-Hosting-SQL02) and CCA9-ApplicationInsights-Prod in TIS-PROD-CCA_Integration-WE-RG all live under Together-Prod. Always state the scope in the document rather than inferring it from a name.

Key Vaults​

EnvironmentKey VaultSubscription
Developmentat-tgca-tis-d-defaultTogether-Fachtest
Fachtestat-tgca-tis-f-defaultTogether-Fachtest
Stageat-tgca-tis-s-defaultTogether-Fachtest
Prodat-tgca-tis-p-defaultTogether-Prod

Source: ../secrets/README.md, which is authoritative for vault naming and the Enterprise Application per environment.

Resource groups, resource naming and subscription identifiers belong in infrastructure/azure/ and are not yet written.

Retired​

EnvironmentRetiredRecord
VUDEVAugust 2026vudev-decommissioning.md
TISDEVlate 2025none β€” see below

TISDEV was deleted before VUDEV and has no decommissioning record. Its remains are still visible: roughly ten repositories carry appsettings.TISDEV.json and nlog.tisdev.config files, and configuration still points at tisdev.servicebytogether.at and at server names such as TISDEV-TISDB001. No survey of that cleanup has been done β€” the VUDEV record is the model for one if it is wanted.