Frequently Asked Question

1. Ownership of Technology

All software applications, platform environments, containerized delivery files (Docker), database architectures (SQL Server / PostgreSQL), automated workflows (n8n), configurations, and associated system logic accessible through this service or deployed within your environment are the exclusive Intellectual Property (IP) of our or partner organization.

2. Hosting is Not Ownership

Purchasing, leasing, maintaining, or providing the physical hardware or cloud infrastructure (such as Amazon Web Services or Google Cloud Platform) to host our software does not grant you ownership, intellectual property rights, or copy rights over the software itself. You are paying for a restricted, non-transferable license to use the system.

3. Usage Restrictions

End users, clients, and system operators are strictly prohibited from performing the following actions:

• Modifying, reverse-engineering, decompiling, or extracting core code, Docker layers, or database schemas.
• Copying, exporting, cloning, or distributing our proprietary automated workflows or system logic.
• Sublicensing, renting, selling, leasing, or redistributing the software stack to any third-party entities.

4. Configuration Rights vs. IP Rights

User-level interactions—including the creation of directory folders, local document routing configurations, or platform prompt engineering—are considered operational adjustments. They do not alter or transfer ownership of the underlying AI, automation engine, or platform infrastructure.

5. License Terms, Maintenance, and AI Model Retirement

• SaaS/PaaS Models: Your license to access cloud environments is tied to an active monthly subscription. Access is suspended immediately upon non-payment.
• In-House/Perpetual Deployments: Perpetual license holders retain the right to execute the software version delivered to them indefinitely on their own hardware. However, technical support, platform optimizations, and security patches are strictly conditioned upon maintaining a valid Annual Maintenance Contract (AMC).
• Lapsed AMC Fees: Allowing an AMC to lapse will freeze your software version. Reinstating support later requires back paying the lapsed period fees and paying mandatory system realignment costs.
• AI Model Lifecycle Liabilities: Third-party AI models have fixed lifecycles. When a legacy model is retired by the vendor (e.g., transitioning from Gemini 2.5 to Gemini 3.1/3.5), the engineering work required to rebuild, prompt-engineer, and migrate your system to the newer model is explicitly excluded from the AMC. Model migrations are treated as separate, mandatory, billable development projects. Failure to execute a migration project prior to a model's retirement date will result in the immediate loss of AI capabilities within your deployment.