Admin Deployment Overview
This guide explains the information to gather and settings to configure when preparing for or managing an on-premise Cognipeer deployment.
For technical infrastructure setup (including Docker, Kubernetes, image registries, environment variables, ports, volume mapping, and operational runbooks), please use the Developer Hub.
What an on-premise deployment gives you
An on-premise deployment lets your organization operate Cognipeer in an environment controlled by your team. This can help with data location, network access, compliance processes, and internal operational policies.
Your deployment team remains responsible for the hosting environment, access controls, backups, monitoring, and upgrades unless your contract says otherwise.
Information to gather before deployment
Prepare:
- License or subscription details from Cognipeer.
- Primary admin name and email address.
- Workspace name and expected user groups.
- Authentication and access requirements.
- Data source locations and security requirements.
- Email or notification requirements.
- Model, embedding, and vector storage decisions.
- Support contacts for your IT, security, and business owner teams.
Do not send secrets through normal documentation or chat channels. Use the secure process agreed with your Cognipeer contact.
Admin setup after installation
After your technical team confirms that Cognipeer is available:
- Sign in with the initial admin account.
- Change any temporary admin credentials.
- Review workspace settings.
- Invite the first workspace admins.
- Configure default model and datasource settings.
- Add required data sources and tools.
- Test a Peer with a small, low-risk datasource.
- Confirm that support and escalation contacts are documented.
License and subscription management
Keep license and subscription ownership clear. Admins should know:
- Which license is active.
- Who owns renewal or subscription changes.
- How to confirm license status in the product.
- Who to contact if the license is close to expiry or fails validation.
See Subscription Management for product-level license guidance.
Support and escalation
Contact your Cognipeer support channel when:
- You cannot access the initial admin account.
- License validation fails.
- Users cannot sign in after setup.
- Workspace settings do not save.
- A critical Peer, Flow, or datasource does not work after deployment.
Provide the product area, affected workspace, approximate time, and user-visible error message. Your deployment team can provide infrastructure logs separately when support requests them.
For technical implementation
Use the Developer Hub for deployment runbooks, Docker and Kubernetes instructions, image registry access, environment variables, ports, volume mapping, operations, upgrades, and infrastructure troubleshooting.