Private workspace for organizations
Your communication.Your workspace.Your intelligence.
Aelix brings communication, organization control, everyday work and a local AI assistant into one organization-bound environment — starting with a validated Windows pilot.
Shared messenger core Organization-scoped roles Local pilot AI
Live product
Validated pilot foundationReal clients, relay, database and organization roles
Aelix AIContext turned into action
One private layer
Work should not be scattered across unrelated tools.
Communication creates decisions. Decisions create tasks. Tasks create knowledge. Aelix keeps that chain intact inside one organizational environment.
Real product, one workspace
Everything stays connected.
These are real working Aelix screens — not concept mockups. Switch between the core parts of the workspace.
01
Communication with context
Direct conversations, team spaces, files and voice stay connected in one calm workspace.
Built into the same workspace Connected to approved context
What works together
A real product surface, not a feature checklist.
Every capability below is tied to the same organization-aware client and the validated pilot workflow.
01Messenger core
Messages, groups, files and calls
Direct conversations, organization groups, file exchange and calls run through the same Aelix client instead of separate tools.
Working in the multi-client pilot
02Organization
Roles enforced by the relay
Organization IDs, owner/admin/user roles and server-side permissions keep administrative actions inside the correct tenant.
Tenant isolation tested
03Work surfaces
Tasks, calendar and documents
Actions and dates can move from conversations into local tasks and events, while shared files remain discoverable in Documents.
Connected to real client history
04Local Aelix AI
Summaries without a cloud model
The pilot assistant works through loopback with locally available chat history for search, summaries, actions and deadlines.
Local pilot assistant
05People & devices
Visible access, practical controls
Owners and admins can review organization members, change supported roles and revoke authorized devices with server-side guardrails.
Owner and admin workflow
06Operations
Licensing, updates and languages
A signed offline-verifiable license, built-in update flow and 26 interface languages support a controlled organizational rollout.
One shared Aelix codebase
52° · 13' · N
Z · 72
Aelix, from every angle
A private layer you can hold onto.
72 Z
Product in motion
See a conversation become action.
This is not a static video layer. The Aelix conversation is playing live in your browser — pause it, switch the scenario or send a message.
LIVE PRODUCT LOOP
# product-launchPilot rollout · 8 members
AELIX AI · LIVEFollowing the conversation
Approved workspace context only
From conversation to action
A workspace that remembers why.
Instead of losing context between chat, calendar and documents, Aelix keeps the reason beside the result.
01
Talk naturally
Message, call, share files and work across private teams.
02
Capture the outcome
Aelix turns discussions into summaries, decisions and owners.
03
Keep knowledge alive
Documents, tasks and context remain connected and searchable.
Decision capturedLaunch pilot with the 5-step onboardingSource: Product team · Today
Next actionSchedule the technical reviewOwner: Alex · Friday
An explicit technical boundary
The relay enforces the organization. Production operations are scoped separately.
The validated pilot uses authenticated clients, a TLS relay, PostgreSQL and an organization-bound signed license. It proves the product foundation without pretending that a local demo is already a customer production environment.
01
Organization-scoped sessionsUsers, devices, roles and administrative requests carry the same organization boundary.
02
Server-side enforcementThe relay checks permissions, license state, user limits and device limits instead of trusting the interface.
03
Deployment discoveryDNS, trusted TLS, backups, identity, monitoring and support ownership are defined before production.
Validated pilot boundaryTLS relay · PostgreSQL · signed organization license
Organization control
People, fixed roles and authorized devices — visible in one place.
The pilot gives owners and administrators a real management surface while the relay remains the authority for every sensitive change.
- Owner, admin and userUse the supported role model with server-side guardrails.
- Authorized device visibilityReview sessions and revoke a device without letting it revoke itself.
- Organization onboardingJoin, create or enter a prepared demo organization from the client.
No roadmap disguised as product
Know exactly what is ready — and what gets scoped next.
Aelix separates a validated pilot foundation from production commitments so a customer can evaluate the real product with a clear boundary.
READY FOR A CONTROLLED PILOTWorking foundation
- Messages, groups, files and calls
- Organization-scoped owner/admin/user roles
- Users and authorized device controls
- Local AI, search, tasks and calendar
- Built-in updates and 26 interface languages
- TLS relay, PostgreSQL and signed licensing
DEFINED BEFORE PRODUCTIONDeployment scope
- Public DNS, trusted TLS and network ownership
- Backup, recovery, monitoring and incident handling
- Production identity, invitations and installer channel
- Organization policies and extended audit coverage
- Customer AI/RAG and external system connectors
- Load, endurance and platform qualification
A practical path forward
From a demo to your own workspace.
Start small, validate the workflow with a real team, then shape deployment around the organization.
Product demonstration
Walk through working communication, organization control, local AI and license flows with your own questions.
Bounded pilot
Select a real team, supported workflows, administrators and measurable success criteria.
Production discovery
Define infrastructure, identity, operations, policies and support before a production commitment.
Turn interest into a concrete next step
Build the first Aelix pilot brief.
Choose the team, primary workflow and starting environment. The planner creates a transparent scope you can copy, review and use for a technical discussion.
Private by designNothing entered here is sent or stored. The brief is generated in your browser.
Contact us directlyinfo@aelix.it.comOpens your email app with a prepared message.
01Your generated scope will appear here.
It will include the validated foundation and the decisions still required before production.
Practical answers
Before you evaluate Aelix.
Clear answers about the current product, local AI, roles, platforms and the path from pilot to production.
01Is Aelix ready for a production company rollout?+
The current validated result is a working Windows pilot foundation: organization isolation, fixed roles, users and devices, messaging, files, calls, local AI, licensing and the first administrative workflows. Public infrastructure, backup and recovery, production identity and organization-specific policies are scoped separately before a real deployment.
02Does the pilot send chat history to an external AI provider?+
No. The demonstrated Aelix AI path uses a local model through loopback and receives only history already available to that client and organization. External providers, enterprise RAG and cross-system knowledge connectors are not presented as finished features.
03Which roles and access controls exist today?+
The foundation provides owner, admin and user roles with a fixed server-side permission set. User and device administration is organization-scoped. Custom roles, a full permission editor, SSO and a complete audit console belong to a later production slice.
04What does the Aelix license control?+
The relay verifies a signed organization-bound license locally. It carries the license type, validity, user and device limits, major version and enabled modules. The private signing key never needs to be installed on the customer relay.
05Which platforms are validated for the first pilot?+
The documented client demonstration and operator workflow are validated on Windows. Other client targets in the shared codebase require a separate qualification step before they are included in a customer commitment.
06How does a company start?+
Start with a product demonstration and a short technical discovery. Then define a bounded pilot team, administrators, required workflows, infrastructure owner and success criteria. The planner below turns those choices into a reusable first brief.
Aelix
Your communication.
Your workspace.
Your next pilot.
Evaluate the working foundation, define the boundary and move forward with evidence instead of assumptions.