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

# Custom Structures

In addition to its core fund product, SIVAX supports custom-built structures for users who require more direct control over product design.

This applies to cases where a standard fund format is not suitable. Requirements may include specific payoff profiles, defined protection ranges, tailored risk budgets, or alignment with treasury and operational objectives.

### Fund Product vs Custom Structures

Custom structures are not the default SIVAX experience.

The core product is a continuously managed fund that provides ongoing access to structured income without requiring users to manage individual positions. Custom structures sit alongside it as a separate capability for more specific use cases. These two product paths serve different needs:

<table><thead><tr><th width="164.49609375">Product Type</th><th width="194.890625">Purpose</th><th width="133.4296875">Control Level</th><th>Experience</th></tr></thead><tbody><tr><td>Fund Product</td><td>Managed participation</td><td>Low</td><td>Continuous, hands-off</td></tr><tr><td>Custom structures </td><td>Tailored construction</td><td>High</td><td>Designed per specific requirements</td></tr></tbody></table>

> The fund product focuses on simplicity and continuity, while custom structures provide flexibility and control.

### What Can Be Customized

Custom structures are built around specific objectives, constraints, and product rules. They may include:

* Principal-protected or risk-bounded designs
* Custom payoff profiles
* Tenor preferences
* Barrier, trigger, or observation conditions
* Capital protection levels
* Income- or treasury-focused objectives
* Policy or mandate-driven risk constraints&#x20;
* Reporting or operational requirements

This provides a level of specificity beyond what a shared fund product is designed to offer.

### When to Use

Custom structures are used for cases that require product-level specificity, mandate alignment, or a tailored operating framework. This includes treasury, distribution, and partner-led structures, or situations where a standard product format is not sufficient. They are designed around defined objectives or constraint sets.

Custom structures involve a more controlled process than the core fund product, including design, review, approval, issuance, reporting, and ongoing monitoring. They require more than a different payoff shape, with closer alignment on documentation, operating parameters, eligibility, and governance over time. They represent a more specific product path rather than a broader version of the core product.

### Requirements

Custom structures may require a more formal participation framework. This can include:

• Permissioned access

• KYC or whitelist requirements

• Jurisdictional or policy controls

• Controlled issuance paths

• Formal reporting expectations

• Additional operational documentation

They define not only payoff design, but also how the product is controlled, delivered, monitored, and documented.


---

# 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:

```
GET https://docs.sivax.io/products/custom-structures.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.