Infrastructure
This section is for the people installing and operating InsightSpace. If your organization already has an installation, use its browser address and start with the Platform guides.
The InsightSpace team supplies the release artifacts, container-registry access, license, and installation procedure. Customers do not need access to the private application source repository.
Plan the installation
Section titled “Plan the installation”The standard planning baseline separates the application server from the GPU inference device. The application server hosts the web application, API, database, document storage, and extraction. The inference device runs the agreed local AI models over a private network connection.
A compact installation can put these services on one device. External database, object-storage, proxy, or model services can be used when agreed for the supplied release. Confirm the topology and capacity with the InsightSpace team before provisioning hardware.
Required capabilities
Section titled “Required capabilities”| Capability | Purpose | Deployment decision |
|---|---|---|
| Web application and API | Browser interface, authentication, permissions, and research orchestration | Two reachable hostnames and trusted HTTPS |
| PostgreSQL with pgvector | Application records and searchable vector indexes | Local database or compatible external service |
| S3-compatible object storage | Uploaded sources and extraction artifacts | Local storage service or external S3-compatible endpoint |
| Document extractor | Converts uploaded files into searchable content | Application server or agreed separate extraction host |
| Chat inference | Produces research answers and working documents | Approved local or external model service |
| Embedding and reranking | Creates the document index and ranks retrieved evidence | Models and endpoints supported by the supplied release |
| SMTP | Invitations, account recovery, and notifications | Client-provided mail service |
| Backups and monitoring | Recovery and day-to-day operation | Named owners, destinations, retention, and checks |
Prepare and hand over
Section titled “Prepare and hand over”- Complete the installation prerequisites: hardware, DNS, TLS, SMTP, administration access, and network rules.
- Review the architecture and decide where each service runs.
- Assign ownership of the components, backups, and incident response.
- Prepare the configuration using the template supplied for your release.
- Follow the supplied installation procedure and verify the service before inviting users.
Verify the installation
Section titled “Verify the installation”Use a dedicated test account and the workshop tutorial for the first functional check. Confirm that a user can sign in, create a workspace, upload the sample PDF, complete indexing, ask a question, open its citations, and export a working document.
Also test the account email flows, check that both hostnames work from a normal user device, and complete a restore check for database and object-storage backups. Record the installed version, service owners, and agreed update procedure in the operator handover.
Updates
Section titled “Updates”Review release notes and the release-specific upgrade instructions before changing an installation. Confirm backups and any migration or reindexing requirements, apply the update, then repeat the functional check above. Use the recovery procedure supplied for that release if validation fails.