OIDC support
Sign in through your existing identity provider, such as Keycloak. Group claims in the token serve as the authoritative source for permissions.
Alcilla.Hub
Alcilla.Hub—enterprise-ready without losing simplicity
OIDC support, a central server for shared knowledge databases, shared Kanban boards, and security by design—Alcilla scales from a single workstation to an enterprise solution without changing its architecture.
OIDC
Central knowledge server
Shared Kanban boards
Security by design
From a single workstation to an enterprise solution
Alcilla runs locally on each workstation and can be extended with a central role for teams—based on the same principles, simply serving more users.
A central server conserves resources
Your central instance can consolidate search services and knowledge databases for all users instead of requiring each instance to index and maintain them separately.
Shared Kanban boards
Boards are stored centrally and protected for the intended user groups through existing IAM/OIDC groups.
Personal and shared company knowledge
Personal content remains local. Approved knowledge is provided centrally and made available in a controlled way to authorized people and groups.
Default-deny search
Areas without matching permissions are silently omitted instead of revealing their existence through an error message. A rate limit also applies per identity.
TLS throughout
Both native TLS and a reverse proxy are supported, keeping the entire sign-in flow consistently encrypted.
What security by design means in practice
Alcilla.Hub capability does not merely mean that Alcilla can support many users. It means that security is considered from the outset.
Use your existing IAM
In centralized operation, users sign in through an existing OIDC-compatible identity provider.
Consolidate resources instead of duplicating them
Rather than having every local instance index the same shared knowledge, the central server maintains shared knowledge databases once and makes them available to authorized users.
No product telemetry
Alcilla transmits no product telemetry. Internal company monitoring can be integrated.
One product core, two operating roles
The single-user workstation and central instance complement each other: personal working data remains local, while shared content is made available centrally in a controlled way.
| Single workstation (local) | Central (shared) | |
|---|---|---|
| Role | Personal workstation | Local workstations plus central instance |
| Personal content | Remains local on the device | Remains on the respective workstations |
| Shared content | Available only locally | Approved knowledge, shared boards, or AI models available centrally |
| Sign-in | No sign-in required | OIDC connection to an existing identity provider |
| Source of permissions | Local system and local configuration | Existing IAM: groups and roles from the OIDC token |
From a single workstation to an enterprise solution
Start locally
Use a single workstation without sign-in and with all functions available.
Connect OIDC
The central role requires sign-in through your identity provider.
Provide services centrally
A central search service can consolidate knowledge and AI models for all users.
Share selectively
Boards and areas can be linked to existing group structures from the identity provider.
Fits into existing enterprise environments
With OIDC, TLS, and a central server, Alcilla integrates into existing identity and network structures instead of creating a separate silo.
OIDC
Native TLS
Central knowledge database
Shared Kanban boards
Plan your Alcilla.Hub rollout
We will show you how Alcilla fits into your existing infrastructure—from a pilot workstation to a central server.