Fig. 01 — Start with the outcome you need

Connect identities, AI and business processes — and stay in control.

§ 01 — Thesis

Vianordis connects people, AI agents, applications, and business processes in one controllable platform — from the first permission to a provable result.

§ 02 — European operation

Vianordis is operated by GoSec Cloud OÜ. The European hosting provider, regions, data locations, subprocessors, and service boundaries are under selection and will be documented before production contracting.

Explore Vianordis See how it works

Identity · authority · policy · action · evidence

EU-operated · GoSec Cloud OÜ

TBD

Governed domains · defined per signed order

§ 03What do you need to achieve?

Start with your outcome — not our architecture

What do you need to achieve?

Choose the goal that brought you here. Each path keeps the business outcome connected to the identity, authority, policy, action, and evidence behind it.

Direction 01

Connect systems and applications

Bring people, services, applications, and workflows into one governed action path without hiding the boundaries between them.

Explore the platform

Direction 02

Control identities and access

Make it clear who or what is acting, why that actor has authority, and which conditions must hold before access is granted.

See identity and authority

Direction 03

Integrate AI safely

Treat AI agents as governed participants with explicit identity, limited authority, policy checks, and human approval where required.

Explore governed AI

Direction 04

Trace decisions and activity

Keep the requester, applicable policy, approvals, execution state, and final evidence connected for later review.

See trust and evidence

§ 04The governed action

Identity · authority · policy · action · evidence — connected, not scattered

Five links in every governed action.

Identity establishes who is acting. Authority defines what they may do. Policy evaluates the conditions. Action records what is requested, approved, executed, or rejected. Evidence makes the decision inspectable afterwards. Vianordis connects the five so an action can be evaluated, approved, and traced.

Identity

Who or what is acting — a person, an AI agent, or a system. FreeIPA realm per customer, Keycloak federation.

Who is acting?

Authority

What that person, agent, or system is permitted to do. Roles and permissions bind consequential actions to the people allowed to take or approve them.

What may they do?

Policy

Which rules apply before, during, and after an action. Conditions are evaluated so a request is permitted, held for approval, or rejected.

Which rules apply?

Action

What is requested, approved, executed, or rejected. Human approval is obtained where required before a consequential change is made.

What happened?

Evidence

What demonstrates how and why the outcome occurred. The sequence is recorded so a decision can be reviewed and inspected afterwards.

Can you prove it?

§ 05Sovereignty

Control requires coordinates — operation, jurisdiction, and evidence, documented

“Sovereignty is not a label. It is the shape of the contract, the region map, and the key custody — documented, inspectable, and recorded. Open code, European operation, and accountable architecture support it; none of them guarantee it on their own.”

— Editorial · § 05 · Sovereignty

01operation

European operation, documented per service.

Vianordis is operated by GoSec Cloud OÜ using documented European hosting infrastructure. The future hosting provider, regions, hardware, processing locations, subprocessors, and GoSec operational responsibilities will be published per service before production contracting; none is implied by a sovereignty label.

02jurisdiction

European jurisdiction and defined legal exposure.

Vianordis is operated by GoSec Cloud OÜ, an Estonian company, under EU law. The contracting entity, hosting regions, and legal jurisdiction are documented, so an organisation can assess its own exposure rather than rely on a claim.

03control

Identity, keys, and residency you can inspect.

FreeIPA realm per customer, Keycloak federation, and OpenBao KMS. Key custody is defined per tenant and data domain through the selected BYOK, CYOK, or HYOK service scope. Data residency is declared, enforced, and recorded as evidence rather than asserted.

§ 06Compliance

Processing terms · data-path documentation · control mappings

§ 06 — Compliance

Customer data for the listed services is stored and processed within the documented EU service scope. Subprocessors and any exceptions are disclosed by service.

— Vianordis · processor agreement, clause 6.2

Regulation · 2016/679

GDPR

GDPR-oriented controls are mapped by service. The applicable DPA, subprocessors, locations, responsibilities, and data-subject-rights procedures are provided with the managed-service contract.

Regulation · 2022/2554

DORA

DORA-related operational-resilience controls are assessed by customer role and service scope; technical controls do not establish customer conformity.

Standard · ISO/IEC 27001

ISMS

Information-security controls are being mapped against ISO/IEC 27001. No certification or completed external audit is claimed without published scope and evidence.

Directive · 2022/2555

NIS2

NIS2-related security and incident-response capabilities are assessed per service and customer role. Reporting duties remain with the responsible organisation.

Regulation · 2024/1689

EU AI Act

AI Act-related controls are assessed by capability, actor role, risk, and deployment context. Disclosure, logging, oversight, and evidence status vary by application.

Regulation · 2025/327

EHDS

EHDS-related capabilities remain in controlled validation. Applicable roles, data uses, consent, pseudonymisation, and evidence require a defined Aether service scope.

§ 07Specialised settings

Sector solutions — Education · Healthcare — controlled Alpha

§ 09 — Specialised settings

Vianordis in specialised settings.

The same Vianordis product, configured for sector-specific workflows, terminology, and governance. Controlled Alpha access is limited and by application.

§ 08Go only as deep as you need.

One journey · five levels of detail

Go only as deep as you need.

Begin with the value, move into real use cases, plan adoption, inspect the architecture, or verify the evidence. The context stays connected as the detail increases.

Level 1

Understand

For everyone

See what Vianordis controls and why connected governance matters.

Understand the model

Level 2

Explore

For business users

Discover applications, use cases, roles, and specialised settings.

Explore applications

Level 3

Apply

For decision makers

Shape a governed operating model and choose a managed-access route.

Plan your route

Level 4

Build

For architects and developers

Inspect boundaries, documentation, integration status, and source availability.

Open documentation

Level 5

Verify

For governance and audit

Review claim scope, release gates, limitations, controls, and evidence.

Open the Trust Centre

Community

Build the Constellation.

Explore, test, contribute, navigate, design, partner, or register European investment interest.

Choose a route

§ 09 — Closing remark

Your goal. Your path. One governed platform.

Start with the outcome you need, then follow the connected path from identity and authority through policy and action to evidence. Explore the platform now, or talk to us about a managed-access route.

Explore the platform Speak to a human

Send us your use case — we’ll show you how we resolve itDescribe the process, decision, or AI action you need to control. We’ll map the actors, rules, approvals, and evidence, then show how Vianordis would approach it.