> For the complete documentation index, see [llms.txt](https://developer.barchart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.barchart.com/networking-options/connectivity-overview.md).

# Connectivity Overview

Institutional clients depend on **high-quality, high-availability market data infrastructure** to support business-critical applications.

Barchart’s Openfeed platform delivers real-time data with **Level 1 and Level 2 market depth**, available through multiple connectivity options including public internet access, private cloud networking, and dedicated cross-connects.

With well-documented protocols and feed handlers, Openfeed minimizes development and operational overhead, allowing teams to spend less time managing infrastructure and more time building products, serving clients, and growing their business.

To support a wide range of technical environments and performance requirements, Barchart offers several connectivity models for accessing Openfeed services.

Clients can choose the architecture that best fits their infrastructure, latency targets, and security policies—from standard internet connections to private cloud networking or ultra-low-latency colocation links. The sections below outline these connectivity options and summarize their typical use cases, performance characteristics, and deployment considerations.

**Connectivity Options**

| Connection Method          | Latency   | Internet Exposure | Typical Users            |
| -------------------------- | --------- | ----------------- | ------------------------ |
| Public Internet            | Moderate  | Yes               | Developers / evaluation  |
| AWS PrivateLink            | Low       | No                | Cloud trading systems    |
| Colocation / Cross-Connect | Ultra-low | No                | HFT / production trading |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.barchart.com/networking-options/connectivity-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.