For IT administrators and technical reviewers
Pelaikan's installed configuration is designed for legal teams that need Microsoft Word integration and local document handling. The Desktop App provides the local runtime; the Word Add-in provides the in-document interface.
Three components work together, with different responsibilities.
A native Windows/macOS application built with Tauri. It renders the Pelaikan interface in a system webview, manages local application permissions, and starts the bundled engine after the user signs in.
A bundled Python runtime exposes a FastAPI service on loopback, normally on port 5050. It performs the heavy local work that browsers and Office add-ins cannot do directly.
An Office.js taskpane hosted from Pelaikan's Firebase site. It reads the active Word document through Microsoft Office APIs and uses the Desktop App's local engine/session for installed workflows.
The installed workflow keeps document-heavy operations on the endpoint and uses cloud services for identity, orchestration, and configured AI/API calls.
The Desktop App authenticates the user and binds the installation to a client identifier. Session tokens are used for authenticated calls to the Pelaikan API and local engine.
The Tauri shell launches the bundled Python sidecar. The engine listens on loopback and exposes local endpoints used by the Desktop App and Word Add-in.
User-selected files are processed locally for document structure, footnotes, citation extraction, OCR, embeddings, and local database search.
Pelaikan attempts local database resolution first where available, then uses configured APIs, web search, cloud libraries, or AI providers for source retrieval and support analysis.
Items commonly reviewed before deployment in managed environments.
The app needs access to user-selected documents, local application data, and local database folders. It does not require inbound network access from other machines.
Allow the app, Word, and the embedded webview to reach 127.0.0.1/localhost on the engine ports used by the installation, primarily 5050 with fallbacks used in development and add-in contexts.
Allow outbound HTTPS to Pelaikan hosting and API domains, Firebase/Google identity services, and Microsoft identity endpoints where configured for sign-in or add-in operation.
The production manifest points Word to the hosted taskpane and declares both Pelaikan cloud domains and localhost engine origins. Centralized deployment can be handled through normal Microsoft 365 add-in administration.
Some citation resolution, OCR, embeddings, and congruence steps may call configured cloud AI or source APIs. Enterprise deployments can review provider choices and regional settings as part of data protection approval.
The engine writes diagnostic logs locally and maintains local SQLite/vector index data for user databases. These files remain under the user's endpoint storage unless your organization backs them up or syncs them separately.
The Desktop App is the trusted local runtime. It holds the permissions needed to read selected files, launch the local engine, and use native networking where browser/webview restrictions would otherwise block localhost traffic. The Word Add-in is a hosted Office interface that relies on Office APIs for document access and the local engine for installed-client workflows.
The cloud backend is primarily the identity, metering, and orchestration layer for installed clients. For web-only use, processing can occur server-side; for Desktop App and Word Add-in use, the architecture is intentionally oriented around local processing and explicit outbound calls.
Read the Data & Privacy PageWe can provide the current manifest, endpoint list, installer details, and data-processing notes for your organization's IT, security, or procurement review.
Request Deployment Details