# Architecture
Freelucy is a **scoped ServiceNow application** that runs entirely inside your ServiceNow instance. It introduces no custom tables, requires no integrations, and reads only the tables your administrators authorize through cross-scope privileges.
The diagram below summarizes the application architecture as of version 3.
Freelucy application architecture (v3).
***
## What this means in practice
* **100% on ServiceNow.** Freelucy runs natively. There is no external service, no integration to configure, no data leaving your instance.
* **No custom tables.** Freelucy uses core ServiceNow constructs — `cmdb_rel_ci`, `cmdb_rel_type`, scoped roles, and cross-scope privileges. Nothing new is introduced into your data model.
* **No additional licenses.** Because no custom tables are added, no additional ServiceNow end-user licenses are required to use Freelucy.
* **Governed access.** Administrators control which tables Freelucy can read (cross-scope privileges) and which class pairs users can connect (suggested relationships). Users only see what your governance allows.
* **Built on Now™ certified.** Freelucy holds ServiceNow's highest technical designation for partner applications, meaning it has been designed and tested for fast, agile, resilient, and secure interaction on the Now Platform.
***
## What's next
* See [Configuration overview](/freelucy/configuration/configuration.md) for the administrator setup that activates this architecture for your users.
* See [Roadmap](broken://pages/nWrXLJKkMqDlySZyHZWr) for upcoming versions and ServiceNow release support.
---
# 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://docs.ins-pi.com/freelucy/reference/architecture.md?ask=
```
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.
