Notes and knowledge
Personal and shared notes, linked content and search with access that fits the agreed encryption model.
YOUR COMPANY APP / CUSTOM DEVELOPMENTOne company.
One company.
Your own communication space.
We develop your communication app: notes, team chats, direct messages, voice, video and connected email. With your design, your workflows and a suitable encryption model. You receive the source code, documentation and a user handbook for your team.
Individual development quote · scope, price and schedule agreed after clarification
Your workspaceMade for you
EXAMPLE · TEAM KNOWLEDGE
A good start for everyone.
Our guide to day one: people, workflows and answers to common questions.
- Meet the people who can help
- Understand shared workflows
Linked to: team handbook
EXAMPLE · PROJECT SPACE
# getting-started
Project team
The workflow draft is ready. Can we go through the open questions together?
Operations
Groups and direct messages that fit your workflowsOf course. The notes are in the project space.
EXAMPLE · TEAM CONVERSATION
Think through the next step together.
VoiceVideoScreen
Project management · IT · Operations
EXAMPLE · SHARED INBOX
Every message has a place.
Planning the project startAssigned to: project team
Documents for the meetingAssigned to: operations
Mailboxes and workflows to fit your needs
Knowledge in one shared place
Personal and shared notes with search that fits the agreed permissions and encryption.
Interactive design concept for a development project. The interface, features and protection model are created within the commissioned project.
Developed for youYour own interface and workflows
Agree protection togetherWith specific testing and acceptance criteria
A documented handoverSource code, documentation and handbooks
WHAT WE CAN DEVELOP FOR YOUWhat connects your team
What connects your team
gets a shared home.
Choose the areas you need with us. We build a solution for your company on suitable open components. The specific feature scope is agreed before development.
Groups and direct messages
Spaces for teams and projects, private conversations, attachments and agreed guest access. With rules for membership, history and changing devices.
Voice calls and video meetings
Voice, video and screen sharing within the agreed device and participant limits. Telephone-network connections and recording are planned separately.
Incoming email and routing
Connect existing mailboxes, assign messages to teams or cases, and design workflows. External email has its own protection boundaries.
Roles and administration
Accounts, team roles and permissions that fit your organisation. Integrate SSO, multi-factor authentication, joining and leaving processes, and guest policies deliberately.
Integrations and support
Connect selected business systems, calendars or workflows through documented interfaces. Agree maintenance, updates and support as a clearly defined operating scope.
FROM YOUR IDEA TO A PROJECT SCOPE
What should your company app do?
Select your initial requirements. We carry your choices into an editable enquiry and discuss the details with you. Price and effort follow from the concept we agree together.
YOUR FIRST PROJECT OUTLINE
Make it concrete together.
Notes and knowledge · Team chat and direct messages
- Team
- Not yet decided
- Operations
- Clarify together
Topics for the concept discussion
- Your design, roles and workflows are defined in the concept.
- For search and notes, we align access rights with encryption.
Your handover includes: Source code, build and installation instructions, architecture and operating documentation, a user handbook, training, tests and acceptance.
Enquire with this selectionThis selection is a starting point for discussion. Your enquiry is sent only when you submit the contact form.
INCLUDED IN THE DEVELOPMENT OFFERYou receive the platform.
You receive the platform.
And the knowledge behind it.
Development ends with an orderly handover. You receive material for everyday use, your IT team and future development. The specific deliverables, usage rights and responsibilities are recorded in your offer.
Self-hosting and handover to another service provider are considered in the plan. Third-party components retain their own licences; provider contracts and export limitations are identified.
- Project source code with agreed usage and modification rights, plus a list of dependencies
- Build and installation instructions: build, configure and deploy the project in the agreed environment
- Architecture documentation covering components, data flows, interfaces and agreed protection boundaries
- Administration handbook for permissions, updates, backup and recovery
- User handbook for the main workflows, plus agreed training for the team and administrators
- Testing and acceptance records: agreed test cases, results and documented outstanding items
- Orderly handover of operating access and the agreed key-management and recovery procedure
FROM REQUIREMENTS TO YOUR OWN SOLUTIONStep by step.
Step by step.
With traceable results.
You do not need a finished specification to start. We translate your everyday work into an agreed feature scope and make decisions visible early.
- 01
Requirements and concept
Understand people, devices, workflows and existing systems together. Outcome: prioritised features, a protection model and a clear initial scope.
- 02
Design and offer
Agree interfaces and key workflows. Describe development, handover, operations and optional reviews with a price and schedule.
- 03
Development and testing
Implement the agreed building blocks and discuss progress. Test functionality, permissions and recovery according to the test plan.
- 04
Acceptance and handover
Review the results together, introduce your team to the solution and hand over source code and documentation. Agree ongoing support and later development stages separately.
SECURITY AS A SPECIFIC COMMISSIONA level of protection
A level of protection
that can be tested.
Together we define which data needs protection and from whom. We select maintained, technically suitable open components and test their integration. We do not invent our own cryptography.
Protection requirements and test plan
Start with a threat model, data categories and verifiable acceptance criteria. Relevant OWASP ASVS requirements inform the agreed test plan.
Encryption and keys
End-to-end encryption for agreed areas, TLS for connections and protection of stored data. Key management and recovery are planned explicitly.
Identity and permissions
MFA, SSO and roles as needed. Device checks, session revocation and offboarding belong in the design; permissions are tested with different user roles.
Operations and recovery
Updates, bounded audit logs, backups and recovery tests within the agreed scope. Operating responsibilities, response times and retention are documented.
An independent penetration test can be commissioned separately. Test scope, findings and acceptance are documented; this does not promise certification or absolute security.
Technical foundations: OWASP ASVS and OWASP on encryption and key management.
IMPORTANT DECISIONS MADE UP FRONTProtected thoughtfully.
Protected thoughtfully.
Explained clearly.
A protected chat does not automatically make every integration end-to-end encrypted. We describe the protection boundary for each feature separately.
External email remains a separate communication channel.
Transport encryption between mail servers is not end-to-end encryption. Importing an inbox does not retroactively protect the route messages took. S/MIME or OpenPGP requires compatible counterparties, clients and keys.
Example: TLS and email encryption explainedSearch and SI need access to content.
With end-to-end encryption and no server keys, ordinary server-side search cannot read message content. Local search on authorised devices is one option. An SI system or bot with content access becomes an additional authorised recipient; that change to the protection boundary must be explicitly agreed.
Background: Matrix on end-to-end encryptionPlan calls, recordings and the telephone network separately.
End-to-end protection for voice and video depends on the participating clients and the chosen architecture. Recording or transcription needs an authorised endpoint with content access. A connection to the public telephone network sits outside the internal encryption boundary. Connection metadata and end-user devices also need protection.
Background: encryption in LiveKitFROM YOUR PROJECT TO A WELL-DEFINED OFFERHow does
How does
your company work?
Tell us what your team needs. We clarify scope and feasibility, propose a suitable architecture and quote development, operations and optional reviews separately.
Request an individual quoteCustom development within an agreed scope, with documented acceptance and handover to your company.
Useful details for getting started
- People and conversationsNumber of users, guests and maximum simultaneous participants in voice or video calls.
- Devices and existing systemsBrowsers, mobile devices, SSO directory, email provider and intended integrations.
- Protection and data accessConfidential areas, search needs, SI, recordings, retention and recovery.
- Operations and prioritiesSelf-hosting or managed operations, responsibilities, budget range and intended initial scope.