A shared app foundation
New apps start in a prepared Svelte app shell with shared navigation and structure. Your employees focus on the task their app needs to solve.
Architecture & standards
Your employees know their workflows and build suitable apps with AI. Your company sets the framework. We set up and maintain the shared foundation so departments can create and improve applications themselves.
Consistent components
Forms, tables and dialogs come from your shared design system. AI uses these components so new applications feel familiar and fit your company.
Clear rules for AI
Project rules define the architecture, components and approved interfaces. They guide AI when creating and changing apps. Technical checks and access controls complement these rules.
Shared business functions
Recurring workflows and interfaces are prepared once and used across apps. Inputs and permissions are checked there; improvements to shared logic benefit other applications.
Development process
We start with a concrete task from your company. We prepare the environment and train your employees. They then describe, test and improve their own applications with AI within the agreed framework.
Start with one app together
We select a manageable use case and build the first app together. Your employees learn to describe requirements, review results and use the prepared workflow.
Describe the need
The department describes the workflow: what should the app solve, who uses it and what data does it need? This expertise gives AI a clear goal.
Develop step by step with AI
AI builds the application using the intended components and functions. Employees try out workflows and request specific improvements until the app fits their actual work.
Review and deploy
Employees review the business result. Prepared technical checks complement this review. Once the agreed approvals are given, changes reach the intended environment through the configured deployment workflow.
Deployment
The path to a running app is part of the shared foundation. We set up deployment, checks and approvals to suit your company. Employees then use the prepared workflow without having to manage servers.
Deploy your own changes
In an implemented project, employees transfer the finished version to the designated app branch. The server detects the change and deploys it automatically. Unfinished changes stay outside that branch.
Only the changed app
Each app runs in its own container and has its own deployment workflow. Employees can deploy their app separately. Other apps and the shared platform do not need to restart.
Check the start
Technical checks accompany deployment. After startup, a health check verifies that the service is reachable. Your employees review the business result using the intended workflows.
Agree on approvals
We define who approves changes and where they are published. In the example project, the app branch deploys automatically; project leads review integration into the shared main branch separately.
Access & operations
Apps built by employees also need controlled access and reliable support. We prepare sign-in, data storage and operations. Together we clarify who is responsible for each app and how the shared technical foundation will be maintained.
Shared sign-in
Employees use a shared sign-in. Access groups determine who may open an app. Permissions are checked technically before access and do not depend on an instruction to AI.
Separate data and permissions
Each app receives the data access it needs and, where required, its own persistent storage. Shared data is accessed through approved interfaces. Technical permissions limit access to other applications.
Responsibility for each app
We agree on business responsibilities, contacts and ongoing costs. Documented workflows and configurations make handover easier when employees change roles or an app is passed on.
Maintain the shared foundation
We maintain the shared technical foundation. We agree on updates, error handling and maintenance of individual apps. Logs support troubleshooting; persistent storage keeps data across app updates.
Example applications
Project planning, time tracking or inventory: departments build apps for their daily work. We bring them together in a shared portal with a consistent entry point and controlled access.
One portal for your apps
The example shows how your applications become accessible in one place. Each app runs in its own container and can be deployed separately. Resource limits control consumption. Updates do not restart other apps; permissions control access.
Tasks and handovers
Teams create checklists and handover records for their own workflows. Tasks, responsibilities and open points remain visible; feedback from daily work informs the next version.
Requests and documents
A department builds a suitable intake process for internal requests or documents. The app shows progress, responsibilities and agreed approvals; access and data storage follow the shared framework.
Equipment and rooms
Employees describe the information they need about equipment or rooms. AI creates lists, forms and filters. Other teams can use the same prepared components and functions.