(Group Docs Viewer for .NET/ java) – for Perpetual Deployment and we will use our brand name

GroupDocs.Total Product Family
1

Deployment & Hosting

Can GroupDocs be deployed on-premise in a fully offline environment?

What are the server requirements for hosting GroupDocs on AWS/Azure?

Is there a limit on the number of concurrent users accessing the viewer?

Does GroupDocs provide any cloud-based hosting options?

Can we use GroupDocs in a microservices architecture?

How does GroupDocs handle multi-region deployment scenarios?

3. Features & Customization

Can the UI be fully customized to match our brand?

How does GroupDocs handle large file streaming for performance optimization?

Does it support DRM features such as watermarking, expiration, and restricted access?

Is annotation access control configurable per user or role?

Can external users (without login) access shared documents securely?

Are there APIs for controlling document expiration and revocation?

Does GroupDocs support live collaboration and multi-user annotations?

Can we restrict downloading, copying, or printing of documents?

4. Support & Future Roadmap

What level of support is included in each licensing tier?

How frequently are updates released, and what is the update policy?

Are there planned features or integrations that will enhance the viewer?

Do you provide a dedicated account manager or support engineer for enterprise customers?

What are the SLAs (Service Level Agreements) for critical bug fixes and security patches?

2

@indrajitsen

Deployment & Hosting

  1. On-Premise Deployment: Yes, GroupDocs can be deployed in a fully offline environment. The API is designed to be independent of the internet, allowing you to integrate it into your corporate internal web applications without requiring an internet connection.

  2. Server Requirements for AWS/Azure: While specific server requirements for hosting GroupDocs on AWS or Azure are not detailed in the provided context, it is generally recommended to follow the standard requirements for hosting .NET or Java applications, which typically include a suitable operating system, sufficient CPU, RAM, and storage based on your expected load and usage.

  3. Concurrent Users Limit: The context does not specify a limit on the number of concurrent users accessing the viewer. However, performance may depend on your server configuration and the resources allocated.

  4. Cloud-Based Hosting Options: The context does not mention specific cloud-based hosting options provided by GroupDocs. It is advisable to check the official GroupDocs website or contact their support for detailed information.

  5. Microservices Architecture: GroupDocs can be integrated into a microservices architecture, as it is a back-end, UI-agnostic API that can be utilized in various application designs.

  6. Multi-Region Deployment: The context does not provide specific details on how GroupDocs handles multi-region deployment scenarios. For this information, it may be best to consult the official documentation or support.

Features & Customization

  1. UI Customization: The UI can be fully customized to match your brand. Since GroupDocs is a back-end API, you can design your own user interface around it.

  2. Large File Streaming: The context does not provide specific details on how GroupDocs handles large file streaming for performance optimization. It is recommended to refer to the official documentation for best practices.

  3. DRM Features: The context does not mention specific DRM features such as watermarking, expiration, and restricted access. For detailed capabilities, please refer to the official documentation.

  4. Annotation Access Control: The context does not specify whether annotation access control is configurable per user or role. This may require further investigation in the official documentation.

  5. External User Access: The context does not clarify if external users can access shared documents securely without logging in. This is another area where the official documentation may provide more insights.

  6. APIs for Document Control: The context does not mention APIs for controlling document expiration and revocation. Please check the official documentation for this functionality.

  7. Live Collaboration: The context does not provide information on whether GroupDocs supports live collaboration and multi-user annotations. For this feature, refer to the official documentation.

  8. Restrictions on Document Actions: The context does not specify if downloading, copying, or printing of documents can be restricted. This may be detailed in the official documentation.

Support & Future Roadmap

  1. Support Levels: The context does not detail the level of support included in each licensing tier. For this information, please consult the official GroupDocs support resources.

  2. Update Frequency: The context does not specify how frequently updates are released or the update policy. This information can typically be found in the official documentation.

  3. Planned Features: The context does not mention any planned features or integrations that will enhance the viewer. For future roadmap details, please refer to the official GroupDocs announcements.

  4. Dedicated Support for Enterprises: The context does not clarify if a dedicated account manager or support engineer is provided for enterprise customers. This may require direct inquiry with GroupDocs.

  5. SLAs for Bug Fixes: The context does not provide information on SLAs for critical bug fixes and security patches. For this, please check the official documentation or contact support.

For more detailed information, I recommend checking the official GroupDocs documentation or reaching out to their support team for specific inquiries.

Sources:
[1]: Aspose.Word Viewer features