> For the complete documentation index, see [llms.txt](https://docs.simplebooth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplebooth.com/hardware-and-gear/lighting/simple-booth-halo-r/rentals.md).

# Rentals

Simple Booth is not offering rentals for one-time event needs at this time

We do not offer rentals at this time. Find alternative options here.&#x20;

***

#### DIY It <a href="#h_f6fedfe1d4" id="h_f6fedfe1d4"></a>

Create your own setup using our [DIY guide](https://www.simplebooth.com/blog/best-diy-photo-booths/). The recommended hardware costs about $150, and you can use it with any of our software plans.

\
See software plan details and pricing [here](https://www.simplebooth.com/plans).

***

#### Find a Local Rental <a href="#h_3d59ae620a" id="h_3d59ae620a"></a>

Search for a local photo booth service that uses Simple Booth products.

\
Local companies may not list the software they use. Contact them directly to confirm.

***

#### Purchase a Booth <a href="#h_6873e65ac4" id="h_6873e65ac4"></a>

For events lasting more than a day or recurring activations, [purchasing an Event Kit](https://buy.simplebooth.com/) is often more cost-effective than repeated rentals.

Our software is subscription-based, but you can cancel unneeded renewals anytime.


---

# 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://docs.simplebooth.com/hardware-and-gear/lighting/simple-booth-halo-r/rentals.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.
