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

# Permanent Session

A Permanent Session is a dedicated EyePop runtime that remains continuously active and ready to process requests without startup or warm-up delays.

Permanent Sessions are designed for production workloads that require low latency, real-time responsiveness, or continuous monitoring.

Unlike on-demand processing environments, a Permanent Session stays running and is dedicated to a single Pop.

### Why Permanent Sessions Exist

Most AI systems require time to establish connections, allocate resources, load models, and initialize processing pipelines before they can begin work.

For many applications, this startup time is acceptable.

However, use cases such as:

* Live camera monitoring
* Real-time alerting
* Interactive applications
* Industrial automation
* Robotics
* Security systems
* Video analytics

often require responses within seconds or milliseconds.

Permanent Sessions eliminate startup delays by keeping your Pop continuously loaded and ready to process incoming data.

### How Permanent Sessions Work

A Permanent Session consists of:

* A dedicated server environment
* One continuously running Pop
* Persistent model loading
* Always-available processing capacity

Because the runtime remains active, requests can begin processing immediately without waiting for infrastructure provisioning or model initialization.

```
Client → Permanent Session → Results

(No startup delay)
```

### Benefits

#### Low Latency

Processing can begin immediately because the runtime and models are already loaded.

#### Predictable Performance

Dedicated resources provide more consistent response times compared to shared or on-demand environments.

#### Real-Time Operation

Ideal for livestreams, camera feeds, and event-driven systems where delays can impact business outcomes.

#### Continuous Monitoring

Supports always-on workflows that must remain active 24/7.

### Common Use Cases

#### Security & Surveillance

* Intrusion detection
* Camera tampering detection
* Loitering alerts
* License plate recognition

#### Industrial Operations

* Safety monitoring
* Equipment utilization tracking
* Forklift detection
* Process compliance

#### Interactive Applications

* Kiosk experiences
* Mobile applications
* Customer-facing AI experiences

#### Live Video Analytics

* Sports analytics
* Crowd monitoring
* Operational intelligence dashboards

### Permanent Sessions vs On-Demand Processing

| Feature                | On-Demand Processing | Permanent Session |
| ---------------------- | -------------------- | ----------------- |
| Startup Time           | May require warm-up  | Always ready      |
| Dedicated Resources    | No                   | Yes               |
| Real-Time Workloads    | Limited              | Optimized         |
| Live Stream Processing | Supported            | Recommended       |
| Continuous Monitoring  | Not ideal            | Ideal             |
| Single Dedicated Pop   | No                   | Yes               |

### Best Practices

Permanent Sessions are most valuable when:

* Response time matters.
* Requests occur continuously throughout the day.
* A camera or stream is monitored 24/7.
* A workflow must be available immediately after an event occurs.

For batch processing, scheduled jobs, or occasional requests, standard on-demand processing may be a more cost-effective option.


---

# 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.eyepop.ai/developer-documentation/permanent-session.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.