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

# Key features

**The developer friendly availability platform**\
A well documented and flexible platform that makes all content available, all the time.  

**The backend for your headless CMS**\
A headless CMS without a content repository is like an electric car without batteries. Instead of building batteries build your chassis. 

**Built for Amazon AWS** \
Run Open Content in AWS, then we can handle upgrades and changes with zero downtime with unlimited storage and backup possibilities.

**Integrated to Naviga Content solutions**\
Works out-of-the-box with solutions such as Newspilot, Digital Writer, Dashboard and Naviga web.

**API’s for everything**\
Use our user interfaces for admin and search, or use the OC REST API:s. Regardless of approach, it’s all open for integration. 

**Reliable backend**\
Spend less time on server issues and let us manage the hosting. Open Content supports a range of different setups, from a small single-node setup to large, clustered, high availability setups.

**Scalable to suit your needs** \
Open Content support both SolR, frontend API and indexing scaling. Open Content scales depending on your needs (and wallet).

**Proven solution**\
Used daily by thousands of Creation users, as well as powering hundreds of apps and sites all over the world.

**Content Types**\
Open Content configuration makes it possible to group content into **Content Type (**&#x74;ypically : Article, Image, Page, Concept, Job, Planning items, Lists, Packages). We have a standardised konfiguration for all tools in the Creation suite.<br>


---

# 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.navigaglobal.com/opencontent/key-features.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.