Identity and access
The 2025 presentation mentions Microsoft Entra ID. For your project, we clarify authentication, roles and required permissions based on the selected components.
FOR IT DECISION-MAKERS
A clear task.
The right architecture.
Technical concept for discussing data sources, model deployment and integration.
SCHEMATIC WORKFLOW · NOT VERIFIED SYSTEM DOCUMENTATION
Users
Question or task
AI platform
Processing & integration
Knowledge & models
Documents, systems and selected model
The sequence, storage and specific connections depend on implementation. External models or services may introduce additional data flows.
INTEGRATION INTO YOUR OWN APPLICATIONS
Your application.
Extended with Mikis.
Mikis can be incorporated into custom developments, such as an internal portal, a business application or a digital workflow.
- LaravelBackend & processes
- NuxtWeb applications
- VueUser interfaces
ReactUser interfaces
The integration is implemented to suit your application and the interfaces required.
Discuss integration ↗MODEL SELECTION
Local models for confidential data.
For confidential content, language models can run directly within your controlled infrastructure. Questions, integrated content and answers are then processed internally. External models can optionally be connected for tasks approved for that purpose.
Data and integration
The existing website describes document integration, database connections and REST APIs. In our technical discussion, we define the data sources, update processes, read or write access and any custom interfaces required.
Confirm before implementation: supported formats, OCR, limits, connectors and error handling.
Models and infrastructure
The language model can also run on your premises. For fully internal processing, document preparation, embeddings and knowledge retrieval are also configured within your controlled environment. We coordinate hardware, network connections and optional external services with your IT team.
Identity and permissions
User management is part of the described setup. SSO methods, document permissions and tenant isolation must be verified against the actual product.
Operation and lifecycle
Updates, backups, monitoring, support and model changes require clear responsibilities. Support is defined according to the agreed scope of services.
YOUR NEXT STEP
Let's explore your environment.
Assess further possibilities selectively.
Capture content in your browser
Earlier documentation describes a browser extension for selected text, web pages and workspaces. Availability, supported browsers and permissions must be verified before any commitment is made.
Languages and usability
Earlier documentation mentions multilingual text and voice features. Target languages, input and output, and accessibility are tested on the specific system.
These capabilities are described in earlier product documentation. We clarify current functionality and suitability for your environment during technical planning; these functions are not enabled in the prototype.