Check In Enterprise Technical FAQs

Product Classification: On-Premise, Self-Contained Standalone Software Application

🌐 Category 1: Infrastructure & Operating Environment

Q: What are the base host operating system (OS) and hardware resource prerequisites?
A: Check In Enterprise runs as a standard Microsoft Windows based computer. It is officially supported on Microsoft distributions (e.g., Windows Server or Windows Desktop Pro). For virtualization environments like VMware vSphere or Hyper-V, our base footprint requires a minimum configuration of 1 vCPUs, 8 GB RAM, and 20 GB of local SSD storage, though resources scale dynamically based on your concurrent check-in volume.
Q: Do you ship your software as a pre-configured Virtual Appliance (OVA/OVF), an installation script, or OCI containers (Docker/Podman)?
A: We provide a downloadable Zip file to be unzipped to a folder. This gives your infrastructure team absolute visibility and control over the underlying environment, ensuring it can be hardened to your internal agency gold images or STIG requirements before installation.
Q: Can we run our own endpoint detection and response (EDR) or antivirus agents on the host OS?
A: Yes. Because the software installs on infrastructure you provision and control, you are free—and encouraged—to run your enterprise security tooling (such as CrowdStrike, Microsoft Defender for Endpoint, or Nessus agents) directly on the host operating system without disrupting the application.

🛡️ Category 2: Network Hardening & Isolation

Q: Does this system require any outbound internet access for licensing verification, telemetry, or error reporting?
A: No. Check In Enterprise is 100% air-gap capable. Node licensing is validated locally via a cryptographic license key file uploaded during installation. The software collects no telemetry and sends zero data back to vendor servers, ensuring absolute network isolation.
Q: How does the web server handle SSL/TLS termination and certificate management?
A: TLS termination occurs entirely locally at the Apache/web server layer. Your network administrators load your agency’s internally issued or trusted CA certificates directly into the server configuration. The application natively supports and strictly enforces TLS 1.3 and strong cipher suites.
Q: Can this application sit behind an existing corporate Web Application Firewall (WAF) or Reverse Proxy?
A: Yes. The application is built to easily integrate behind enterprise reverse proxies and WAFs (such as F5 BIG-IP, Cloudflare Magic WAN, or NGINX). It respects standard X-Forwarded-For headers to ensure accurate client IP logging for your internal auditing.

💾 Category 3: Data Management & Backups

Q: How are database backups handled, and where are they stored?
A: Because the system is self-contained, backups are managed locally via your existing enterprise backup policies. Your team can schedule standard local database of the entire software and database files.
Q: Does your technical support team ever require remote access (e.g., SSH, VPN) to the server for troubleshooting?
A: No, never. We maintain a zero-trust support model. If troubleshooting is required, your administrators can generate anonymized, local error logs to share with us. Our team will never ask for, nor do we require, remote network access or credentials to your environment.
Q: What is the local data retention and purge policy?
A: Check In Enterprise gives agency administrators full control over data sovereignty. The application features built-in configuration settings allowing you to define custom data retention thresholds (e.g., automatically purging or anonymizing check-in records after 30, 60, or 90 days) to comply with local privacy laws and minimize data hoarding.

🔑 Category 4: Identity & Vulnerability Management

Q: How are software patches, bug fixes, and security updates delivered?
A: Updates are delivered via a secure, standalone update package made available through our authenticated customer portal. Your IT team downloads the package, verifies its SHA-256 checksum, and applies it manually during a standard internal maintenance window using your local change control workflows.