Installation
Wissano runs through Docker on your infrastructure. The server delivers the backend and built interface.
Wissano runs on your infrastructure. Documents, users, search index and database remain in your network. Choose local models or deliberately connect an external provider without locking your knowledge into one platform.
Choosing a server region alone does not answer who processes your knowledge, how long content is retained or what happens when a vendor changes its terms. Wissano separates knowledge management from a mandatory cloud service.
You decide the entire operating path. The application can work with local models fully inside your network. Alternatively, connect a provider of your choice and see which service is used for chat or embeddings.
Wissano runs through Docker on your infrastructure. The server delivers the backend and built interface.
Local models keep processing inside the network. External APIs are used only when deliberately configured.
Administrators assign users and documents to knowledge spaces. Restricted content appears nowhere else.
Administrators see document status, knowledge space and processing directly in the library. Connected folders synchronize under your control while original files remain untouched.
Backups protect documents, database and settings together, keeping operational responsibility in your hands.
Yes. With local models through Ollama, local text recognition and locally stored documents, processing can remain fully inside your network.
No. You can configure local and external providers freely. The important part is that the choice remains yours and is not hardwired into Wissano.
Configured keys are encrypted with AES-256-GCM in the database and are never returned in plain text.
You receive a concrete assessment by email. No phone call required.