Altinn Studio is how Norwegian public agencies build, deploy and run digital services on Altinn 3. Service owners build apps in Designer, from simple forms to processes with signing and payment, and switch to code where they need to.
To build apps, start with docs.altinn.studio and its introductory course. This repository is for developing Altinn Studio itself. CONTRIBUTING.md says how we work, the glossary defines the terms we use, and docs/ holds the docs that span components.
Altinn Studio spans Core, Runtime and Platform:
- Core is the control plane, which reaches out to Runtime and Platform. Service owners build, configure and deploy their apps in Designer, with help from the Studio Assistant, and the apps' repositories are in Gitea.
- Runtime is a service owner's own runtime, where its apps run. It is mostly data plane, such as the apps and the workflow engine, with the control plane services that belong to one service owner, such as the gateway and the operator.
- Platform is the shared data plane that apps call, such as Storage, Authorization, Receipt and pdf3. Most of it lives in other repositories.
The architecture diagram goes a level deeper. It shows what runs in Core, Runtime and Platform, and how a deployment and a user's request travel between them.
App developers run apps on their own machines with studioctl, which runs localtest in place of Runtime and Platform. The code is in src/, the cluster configuration in infra/ and charts/, and the workflows in .github/, with their conventions in docs/cicd.md.
Altinn Studio is licensed under the MIT License.