Customer’s Canvas

Beyond the initial license fee, the total cost of ownership involves ongoing expenses for maintenance, potential setup assistance, and support, which are structured to ensure the longevity and reliability of the software component.

• An upfront License Agreement fee grants the client the right to use, install, and operate the Customer's Canvas product within the agreed terms.
• Additional costs are incurred for the ongoing Maintenance Subscription, which provides access to critical updates, patches, and the most current feature releases.
• Setup costs may apply if the client opts for the vendor's Professional Services or expert assistance for integration, custom development, or initial server deployment configuration.
• Clients must budget for their own internal hosting environment (VPS or dedicated server) resources and management, as the product is typically self-hosted.
• Support is often integrated into the Maintenance Subscription cost, ensuring access to technical assistance for troubleshooting and resolving implementation issues.

The vendor provides robust, solution-oriented support backed by comprehensive documentation and professional services, aimed at ensuring clients can effectively utilize, integrate, and maintain the software component within their unique IT infrastructure.

• The vendor offers top-notch and responsive technical support channels to assist customers with troubleshooting and configuration questions.
• Professional services are available for both initial setup and complex integration tasks, providing expert assistance tailored to individual implementation challenges.
• A range of documentation is provided, including user manuals, administrator guides, and developer documentation necessary for API integration and customization.
• Training resources, such as tutorials, videos, and guides, are typically available to help users master the online editor features and manage the template creation process.
• The support team is described as being focused on solutions, often working collaboratively with clients to rapidly deploy new products or resolve technical issues promptly.

Security measures are a combination of the component's architecture—which separates it from the host database—and the client's internal security protocols for managing their self-hosted server environment.

• The application operates in a non-intrusive manner, functioning as a dedicated web application component that does not directly extend to or alter the host e-commerce platform's database or core scripts.
• Customer data protection is primarily managed by the client, as the product is typically self-hosted on the client’s own server or VPS, allowing them direct control over physical and network security.
• The component utilizes open JavaScript API communication, which should be secured using standard industry protocols (like TLS encryption) for all data transferred between the host site and the editor.
• The licensing mechanism relies on a License Key for operation, which acts as a fundamental layer of access control and authorization for the software itself.
• Clients are responsible for applying their own internal organizational and technical security measures, including firewalls, access controls, and regular server patching, on the hosting environment.

The platform features a commitment to continuous improvement, with regular updates that introduce new features, optimize performance, and ensure compatibility, managed through the Maintenance Subscription.

• Features are constantly updated and enhanced, demonstrating an ongoing effort by the vendor to maintain the solution's quality and competitive edge in the market.
• Software updates and new releases are provided to clients who maintain an active Maintenance Subscription, which is required to access the latest versions.
• Update management is typically handled by the client's IT team, as the solution is self-hosted and requires new software files to be installed on the customer’s dedicated server.
• Updates often include performance improvements to the in-house rendering engine to ensure accurate and fast generation of print-ready output files.
• Patches and bug fixes are delivered as part of the update cycle, ensuring the stability and security of the design editor component.

Due to the self-hosted nature of the solution, the client retains clear ownership and control over their customer, order, and design data, which resides directly on their managed server infrastructure.

• Data ownership rests definitively with the client, as all transactional data, design files, and generated print-ready files are stored on the customer's privately managed server or VPS.
• The solution supports data portability by allowing the client full administrative control over the database and file storage location where templates, customer designs, and final output are kept.
• The editor facilitates the creation of print-ready files using its rendering engine, which are output in standard industry formats for easy retrieval and use with external printing equipment.
• The design component maintains a separation of concerns, ensuring that the client’s proprietary business logic and customer data remain segregated from the core editor application logic.
• Data retention and deletion policies are set and enforced by the client, who manages the entire server environment and database backups.

Scaling primarily involves adjusting the hardware resources of the client's hosting environment, which grants them flexibility in managing capacity based on current and anticipated personalization demand.

• Scaling is directly tied to the system requirements of the host server, where increased traffic or order volume necessitates upgrading CPU, RAM, and network capacity.
• The software architecture, utilizing a dedicated web application, allows for scaling resources such as a single-CPU Xeon machine with 16GB of RAM as a starting point, with vertical or horizontal scaling available.
• The required disk storage capacity scales with the business application, specifically increasing as more stock templates are published and more customer orders are processed and saved.
• Scaling up requires the client to coordinate with their hosting provider (VPS or dedicated server) to allocate more resources to the machine hosting the Customer's Canvas application.
• The open API structure supports integration into large-scale e-commerce architectures, enabling high transaction volumes by efficiently handling the communication load.

Contractual terms are governed by the Customer's Canvas License Agreement, which details the use rights and, critically, outlines the fees associated with renewing the necessary Maintenance Subscription.

• The primary contractual obligation after the initial purchase is the renewal of the Maintenance Subscription, which keeps the software licensed and eligible for updates.
• The contract stipulates tiered penalty fees for renewing a Maintenance Subscription that has been allowed to expire, encouraging timely renewal.
• Extension fees for the Maintenance Subscription range from 0% of the extension fee (if expired less than one month) up to 75% of the fee (if expired between 8 and 12 months).
• If the client fails to accept the terms or declines the Agreement, they must cease use, installation, or operation of the product, with any payments made prior to acceptance typically being refunded.
• The licensing terms ensure that continued access to updates and support services is dependent upon maintaining the subscription and adhering to the defined renewal clauses.

As a highly integrated software component, its compliance relies on its adherence to general security best practices and the client’s architecture meeting specific regulatory requirements relevant to their location and customer data.

• The component is designed to be integrated into e-commerce ecosystems, requiring it to function in a manner that supports the client's compliance with general data protection regulations (e.g., GDPR, CCPA).
• The licensing agreement reserves the right for the vendor to refuse acceptance of the contract, ensuring that they can vet potential use cases against their internal compliance guidelines.
• Since the client hosts the solution, they are ultimately responsible for configuring the hosting environment to meet standards like PCI DSS (if handling payment data on the same server) or specific industry regulations.
• The system's non-intrusive nature, utilizing an API and iframe, helps clients maintain separation between the design component and sensitive data regulated by standards like HIPAA (though its use in healthcare is niche).
• Compliance with security protocols is managed through the Maintenance Subscription, which ensures that clients receive security patches and updates necessary to maintain a compliant operational environment.