> For the complete documentation index, see [llms.txt](https://docs.netmap.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.netmap.dev/product-introduction/supported-use-cases.md).

# Supported Use Cases

NetMap supports:

* Maintaining a self-hosted network inventory.
* Mapping physical and logical topology.
* Tracking VLANs, sites, and device relationships.
* Monitoring device and service health.
* Reviewing discovery changes before applying them to inventory.
* Managing IP subnets, reservations, DHCP leases, and conflicts.
* Searching firewall/syslog events.
* Exporting inventory, reports, backups, and logs.
* Automating workflows through API-key-authenticated REST calls.

NetMap is not documented as a horizontally scaled service in the current source. The supported deployment described here is a single all-in-one container with persistent SQLite storage.

## Good Fit

NetMap is a good fit when you want:

* one self-hosted network operations dashboard;
* local control of data;
* Docker-based deployment;
* REST automation with API keys;
* syslog search without running a separate logging stack;
* lightweight IPAM tied to inventory and VLAN metadata.

## Poor Fit Or Requires Maintainer Design

NetMap is not currently documented as:

* a multi-node clustered application;
* a hosted SaaS service;
* a replacement for a full SIEM;
* a high-scale time-series monitoring database;
* a native package-managed service.

Documentation gap: this behaviour could not be verified from the current source for scaling beyond the single-container SQLite deployment.

## Related Pages

* [Architecture](/product-introduction/architecture.md)
* [Quick Start](/installation/quick-start.md)
* [API Capability Matrix](/api/capability-matrix.md)


---

# 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.netmap.dev/product-introduction/supported-use-cases.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.