Local single-user workstation
Alcilla runs on your computer. Emails, notes, chat histories, and all working data remain exclusively local. Ideal for getting started or for sensitive areas of work.
Details ->Your choice
Run Alcilla in the way that best meets your requirements
Alcilla adapts to your business. Start on a single workstation, use Nexus as an intelligent KI loadbalancer across your own infrastructure, or outsource compute-intensive services through Station. You decide: What stays local? What may be processed externally?
Local single-user workstation
Centralized multi-user operation
Intelligent KI loadbalancing with Nexus
Alcilla.Station for AI & additional services
Flexible combinations possible
Four ways to use Alcilla
The operating models are not mutually exclusive. You can combine them and run different functions in different locations.
Centralized multi-user operation
Each person has a local instance, supplemented by a central service for shared knowledge and Kanban boards. Personal content remains private, while company knowledge is shared.
Details ->
Alcilla.Nexus—intelligent KI loadbalancer for your infrastructure
Do you operate one or more AI servers in your own infrastructure? Nexus is the intelligent mediation layer with adaptive load balancing, health monitoring, and failover. We supply the loadbalancer, not the AI infrastructure.
Details ->
Alcilla.Station—AI services from Alaska.Labs
Compute-intensive AI models, document conversion, transcription, and research can run through Alcilla.Station. We provide and fully operate multiple AI servers—you pay for usage, not infrastructure.
Details ->
Why this flexibility?
Every business is different
Some organizations must keep everything local, while others prefer to outsource AI services. Alcilla adapts to you—not the other way around.
Scalable step by step
Start locally on one workstation. Once the approach has proven itself, add shared functions or external AI services—while retaining control at every stage.
Mix and match
Emails stay local, shared knowledge is centralized or accessed through Nexus, and AI models come from Station. Each function can run in a different location.
Common Questions about Operating Models
-
With local operation, Alcilla runs on a single workstation. Personal content such as emails, notes, chat history, local knowledge bases, and Recorder contents can be processed on your own device.
With centralized operation, there is additionally a central instance for shared content. This can provide shared knowledge or Kanban boards for multiple users. Personal content remains on each respective workstation.
-
With the local operating model, personal work data remains on the respective device. This may include emails, notes, chat history, local knowledge bases, Recorder contents, and other work data.
External connections only occur when corresponding services are actively configured, such as mail servers, calendars, file servers, research services, or external model endpoints.
-
Alcilla.Station is a managed service from Alaska.Labs. Resource-intensive functions such as document conversion, transcription, search, research, and AI models are operated on our infrastructure.
Alcilla.Nexus is intended for companies with their own AI infrastructure. Your AI servers process your data within your environment. Nexus bundles your servers and provides a unified interface to local Alcilla workstations.
Short answer: Station is right if you want to outsource AI services. Nexus is right if you run your own AI servers and want to make them centrally accessible.
-
Alcilla.Hub is designed for central team and enterprise functions. These include shared knowledge bases, shared Kanban boards, OIDC login, and access control management through existing group structures.
Alcilla.Nexus, on the other hand, is the intermediary layer for AI servers. Nexus bundles your own AI infrastructure, distributes requests, and provides a consistent AI interface to local Alcilla workstations.
Hub organizes your shared content and permissions. Nexus organizes access to your AI servers.
-
Yes. The operating models do not exclude each other. Alcilla.Desk can start locally and later be extended with central services, Alcilla.Hub, Alcilla.Nexus, or Alcilla.Station.
For example, emails can remain local while shared knowledge is provided centrally via Hub. AI models can be used locally, through your own AI servers with Nexus, or via Alcilla.Station.
-
No. Alcilla does not require any specific AI infrastructure. You can use local models, connect existing AI servers via Nexus, or outsource resource-intensive services via Station.
If you do not want to operate your own AI hardware, Alcilla.Station is the easiest way to use AI features without your own infrastructure. If you are planning to acquire AI servers, we would be happy to advise you.
-
External systems are only accessed when they are actively configured. These may include mail servers, calendars, file servers, model endpoints, research services, or Alcilla.Station.
You maintain control over which services are connected and which functions remain local.
-
Offline work is possible for local and already synchronized content. This includes local notes, locally stored content, or already available knowledge bases.
Functions that require external services naturally need an internet connection. These include mail servers, calendar synchronization, external research, or outsourced AI services.
-
Yes. You can start with a local workstation and later expand Alcilla.
Typical next steps include connecting additional services, using shared Kanban boards, building central knowledge bases via Alcilla.Hub, bundling your own AI servers via Alcilla.Nexus, or outsourcing resource-intensive functions to Alcilla.Station.
Which model is right for you?
We are happy to advise you on selecting and combining the appropriate operating models. Whether you use your own AI infrastructure with Nexus or outsource services via Station, we will help you find the right setup.