> For the complete documentation index, see [llms.txt](https://docs.zigiwave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigiwave.com/zigiops-faq.md).

# ZigiOps FAQ

These are the questions our support and sales teams hear most often from prospects and customers evaluating ZigiOps. They cover how ZigiOps is deployed, how licensing works, how deep the integrations go, and how the platform evolves over time.

## Quick Answers at a Glance

| Theme                    | Question                                         | Short Answer                                         |
| ------------------------ | ------------------------------------------------ | ---------------------------------------------------- |
| Deployment & Setup       | What deployment options are supported?           | On-premises and cloud (SaaS), your choice.           |
| Deployment & Setup       | Is there a difference between on-prem and cloud? | Same core functionality in both.                     |
| Deployment & Setup       | Which one is better, cloud or on-prem?           | Depends on your infrastructure and compliance needs. |
| Licensing & Data Volume  | Is there a limit on records transferred?         | No, licensing is flat per integration.               |
| Integration Capabilities | Does ZigiOps sync comments and attachments?      | Yes, bi-directionally for most systems.              |
| Integration Capabilities | Does it support complex use cases?               | Yes, including logic, mappings, and filtering.       |
| Platform & Ease of Use   | Is it entirely no-code?                          | Yes, 100% configured through the UI.                 |
| Platform & Ease of Use   | Is the platform under continuous development?    | Yes, updated regularly with new features.            |

## Deployment & Setup

<details>

<summary>What deployment options are supported?</summary>

ZigiOps runs both on-premises and in the cloud as SaaS. You choose the model that fits your infrastructure, security policies, and available IT resources, and both options deliver the same integration capabilities, just hosted differently.

</details>

<details>

<summary>Is there a difference between the on-premises and cloud versions?</summary>

The core functionality is identical across both versions. Some advanced features may reach the cloud version first, but general capabilities stay consistent no matter which deployment you pick.

</details>

<details>

<summary>Which one is better, cloud or on-premises?</summary>

Neither option is objectively better, it depends on your requirements. Cloud is ideal if you want a fast start with no infrastructure to maintain, since hosting is handled for you. On-premises is the right choice for organizations with strict security or compliance requirements, since all data stays entirely within your own environment, a deployment option many competitors don't offer.

</details>

## Licensing & Data Volume

<details>

<summary>Is there a limit on the number of records transferred?</summary>

No. ZigiOps has no limitations on data volume. The license is flat and per integration, so you can transfer as many tickets, events, or records as you need without hitting a data cap or paying more as volume grows.

</details>

## Integration Capabilities

<details>

<summary>Does ZigiOps support comments and attachments?</summary>

Yes. For most supported systems, comments and attachments sync bi-directionally, right along with all standard and custom fields, so full context carries over between the connected systems.

</details>

<details>

<summary>Does ZigiOps support complex use cases?</summary>

Yes. ZigiOps handles advanced scenarios such as multi-system integrations, conditional logic, custom field mappings, data transformations, and filtering, and every one of these is fully configurable through the interface.

</details>

## Platform & Ease of Use

<details>

<summary>Is it entirely no-code?</summary>

Yes, 100%. The entire configuration, including mappings, filters, and transformations, is done through the UI. No scripting or custom code is required at any stage.

</details>

<details>

<summary>Is the platform under continuous development?</summary>

Yes. New features, connectors, and enhancements are delivered through regular updates, keeping ZigiOps aligned with evolving integration needs and new system versions.

</details>

***

**Still have questions?** Explore the full list of [supported systems and integrations](https://www.zigiwave.com/integrations/) or check [ZigiOps pricing and licensing details](https://www.zigiwave.com/zigiops-pricing) to find the right fit for your team.


---

# 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://docs.zigiwave.com/zigiops-faq.md?ask=<question>&goal=<endgoal>
```

`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.