# What is Engine?

{% hint style="info" %}
Engine was the pre-cursor to PlaceOS. These guides are provided as a reference for existing deployments. For up-to-date information on the current platform, head on over to [placeos.com](https://placeos.com).
{% endhint %}

* **Software only** built on the modern web.
* **Open source** continuously improved and backed by a full-time team of developers.
* **Extensible** able to run stand-alone, or integrated into staff, building or third party apps.
* **Vendor agnostic** designed to bridge multiple disparate systems.
* **Scale-able** from rooms, to buildings, to precincts.
* **Distributed** multi-node replication for live backup and fail-over.
* **Secure** audit-able interaction with the physical environment and encrypted device communication.

The platform handles the low level device communication, system management and connectivity with user interfaces so that you can focus on how these combine to create intuitive, modern, connected environments.

Designed to run within your on-prem environment or private cloud the entire stack is open to ensure the privacy of your organisation and users is respected.

Deployments running today integrate tens of thousands of devices and services into unique experiences designed to improve health and happiness for staff and tenants.

There are no restrictions on what can be built, but here are some examples of [what's possible](https://acaprojects.com/#spotlight).

## Who builds it?

[Place Technology](https://place.technology) is a team of developers, designers and technologists based across Australia, Singapore, Hong Kong, Shanghai and London. We believe in modern tech and despise black boxes.


---

# Agent Instructions: 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://engine.place.technology/master.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.