> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/on-premise.md). # On-Premise - [What do I need to have my own Navixy instance?](https://navixy.com/docs/qna/on-premise/prerequisites.md): Provision a server, obtain a license, assemble a technician team, register domain names. Optional: SSL certificates and SMS/email gateways - [On-Premise licensing FAQ](https://navixy.com/docs/qna/on-premise/on-premise-licensing-faq.md): Navixy On-Premise license authorizes one platform instance; request additional instances from sales and understand how the license key is validated - [Demo (trial) On-Premise instance FAQ](https://navixy.com/docs/qna/on-premise/demo-trial-on-premise-instance-faq.md): Request and manage trial licenses. Test functionality, features, and installation on your infrastructure within a limited timeframe - [On-Premise updates FAQ](https://navixy.com/docs/qna/on-premise/on-premise-updates-faq.md): Update your instance on your own schedule, no automatic delivery. Major versions every 2–4 months; minor versions released frequently with fixes - [Deployment overview](https://navixy.com/docs/qna/on-premise/deployment-overview.md): Choose your installation method and deployment scenario. Single-server, dedicated DB, Linux, or Windows configurations for any instance size - [What hardware to use?](https://navixy.com/docs/qna/on-premise/deployment-overview/what-hardware-to-use.md): Minimum: 4 CPU cores, 8 GB RAM, 500 GB SSD storage. Physical or virtual servers work; use dedicated DB for 5000+ active devices - [What operating system to choose?](https://navixy.com/docs/qna/on-premise/deployment-overview/what-operation-system-to-choose.md): Ubuntu recommended for ease of maintenance and stability. Linux or Windows supported; OS administration handled by your technical team - [How to install the platform?](https://navixy.com/docs/qna/on-premise/deployment-overview/how-to-install-the-platform.md): Download and install via easy 3-command wizard or advanced Linux/Windows scripts. Docker or manual setup, scale from 500 to 5000+ assets - [How to update the platform?](https://navixy.com/docs/qna/on-premise/deployment-overview/how-to-update-the-platform.md): Run automated update scripts on Linux or perform manual updates on Windows. Back up database before starting to enable rollback if needed - [How to prepare for the update?](https://navixy.com/docs/qna/on-premise/deployment-overview/how-to-prepare-for-the-update.md): Verify Java and MySQL versions meet current requirements. Upgrade software components before platform updates to prevent service failure - [Where and how is data stored?](https://navixy.com/docs/qna/on-premise/where-and-how-is-data-stored.md): MySQL database stores tracking and business data. Images stored in API-server subdirectories. Two databases: tracking and google - [Fault tolerance and disaster recovery](https://navixy.com/docs/qna/on-premise/fault-tolerance-and-disaster-recovery.md): Back up and replicate the database to separate servers. Maintain a standby application copy and DB replica in remote infrastructure - [Why isn't my model connecting to standalone?](https://navixy.com/docs/qna/on-premise/why-isnt-my-model-connecting-to-standalone.md): Device model won't connect: verify the required port is open using nc. Check the device list page for the model-specific port number - [Run instance in a classified environment](https://navixy.com/docs/qna/on-premise/run-instance-in-a-classified-environment.md): Isolate from external network with a private device subnet. Licensing, maps, and geocoding require outbound access to Navixy servers - [Domain requirements for On-Premise](https://navixy.com/docs/qna/on-premise/domain-requirements-for-on-premise.md): Register an A-type DNS record pointing to your server to enable SSL certificates and HTTPS. Optional: separate domains for API and admin panel - [Network requirements for On-Premise](https://navixy.com/docs/qna/on-premise/network-requirements-for-on-premise.md): Open ports: 80, 443 (HTTP/HTTPS), 8383 (WebSocket), 32233 (license), 123 (NTP), device ports. Allow outbound access to Navixy servers - [Green "We'll be back soon" page](https://navixy.com/docs/qna/on-premise/green-well-be-back-soon-page.md): API server is inoperable or domain configuration mismatch. Check service status or validate domain settings in Admin Panel and Nginx - [Manage admin credentials (On-premise)](https://navixy.com/docs/qna/on-premise/manage-admin-credentials-on-premise.md): Rename admin account in the google.dealers table or reset password via API server. Log in to Admin Panel and use the password change feature - [Technician admin accounts for On-Premise](https://navixy.com/docs/qna/on-premise/technician-admin-accounts-for-on-premise.md): Create unlimited technician accounts via SQL INSERT. Change login, title, and password post-creation via Admin Panel. No additional charge - [Reseller functionality in On-Premise](https://navixy.com/docs/qna/on-premise/reseller-functionality-in-on-premise.md): Reseller functionality is unavailable in On-Premise. Deploy a separate licensed instance for each reseller customer instead --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://navixy.com/docs/qna/on-premise.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.