> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neuro-tech.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Operate a Neuron

> Install, configure, secure, update, and troubleshoot a Neuron server

A **Neuron** is the server runtime at the center of the Neuro platform. It combines an HTTPS server, an XMPP broker, identity and contract services, package hosting, persistence, scripting, and operational tooling in one extensible process.

This section is for operators and developers who run a Neuron. It covers installation, initial setup, access control, monitoring, updates, and troubleshooting.

## Choose your task

<CardGroup cols={2}>
  <Card title="Install a Neuron" icon="download" href="/operations/install">
    Prepare a Windows host, open the required ports, and run the installer.
  </Card>

  <Card title="Complete first-run setup" icon="list-check" href="/operations/first-run">
    Configure persistence, backups, networking, XMPP, and the server identity.
  </Card>

  <Card title="Automate configuration" icon="gears" href="/operations/configuration">
    Use environment variables and `Gateway.config` for repeatable deployments.
  </Card>

  <Card title="Manage access" icon="users-gear" href="/operations/users-and-roles">
    Create users and roles, then grant the minimum privileges required.
  </Card>

  <Card title="Install packages" icon="box-open" href="/operations/software-packages">
    Extend a Neuron with signed content and assembly packages.
  </Card>

  <Card title="Troubleshoot" icon="stethoscope" href="/operations/troubleshooting">
    Work from event logs, protocol sniffers, exception reports, and service state.
  </Card>
</CardGroup>

## Runtime layers

| Layer           | Responsibility                                                                 |
| --------------- | ------------------------------------------------------------------------------ |
| Host            | Windows service lifecycle, process identity, firewall, certificates, files     |
| Gateway runtime | Module discovery, configuration, scheduling, persistence, events               |
| Protocols       | HTTP/HTTPS, XMPP client-to-server and server-to-server, SMTP, optional proxies |
| Neuro services  | Accounts, legal identities, contracts, wallet, tokens, ledger, Agent API       |
| Extensions      | Signed packages containing web content, scripts, schemas, or .NET assemblies   |

<Warning>
  Treat the Neuron program-data folder, database keys, TLS keys, API secrets, package keys, and JWT secrets as production credentials. Back them up securely and never commit them to source control.
</Warning>

## Production checklist

* Use a stable domain name with correct DNS records.
* Enable HTTPS and validate renewal before exposing the server.
* Restrict administrative resources and RDP to trusted networks.
* Configure automatic backups and test restoration.
* Create role-specific accounts instead of sharing an administrator account.
* Review the event log and exception log after every deployment.
* Keep package signing keys separate from the Neuron host.
* Enable protocol sniffers only while diagnosing a problem; captures can contain sensitive data.

## Related developer guides

* [Build a Neuron package](/neuron-development/building-packages)
* [Connect an MCP client](/mcp/connect-a-client)
* [Use the Script engine](/script/quickstart)
* [Integrate with the Agent API](/neuron-api/quickstart)