---
title: "Contact Pylon: support, security, and hosting"
description: "How to reach Pylon: support@pylonsync.com for the framework, GitHub issues for bugs, security@pylonsync.com for vulnerabilities, and Stack0 Cloud for hosting and billing. Built in Dallas, Texas."
url: "https://www.pylonsync.com/contact"
---

# Contact

Pylon is built in Dallas, Texas, by a small team. There is no contact form and no gate: write to the address that matches what you need and a person reads it. For anything reproducible, a GitHub issue is faster than email — it goes straight to the people who can fix it.

## Support

Questions about the framework, a bug you hit, or something the docs do not answer. Include your Pylon version (\`pylon --version\`) and what you ran.

[support@pylonsync.com](mailto:support@pylonsync.com)

## Bugs and feature requests

The fastest route for anything reproducible. Issues are public, so other people find the answer too, and a fix lands in a release rather than in one inbox.

[github.com/pylonsync/pylon/issues](https://github.com/pylonsync/pylon/issues)

## Security

Report a vulnerability privately. Do not open a public issue for a security problem. We confirm receipt and keep you updated until it is fixed.

[security@pylonsync.com](mailto:security@pylonsync.com)

## Hosting and billing

Anything about a Stack0 Cloud project: deploys, custom domains, usage, or an invoice. Sign in first and the dashboard shows the project the question is about.

[cloud.stack0.dev](https://cloud.stack0.dev)

## Privacy

Data requests, deletion, and anything covered by the privacy policy.

[privacy@pylonsync.com](mailto:privacy@pylonsync.com)

## Legal

Terms, licensing, and contracts.

[legal@pylonsync.com](mailto:legal@pylonsync.com)

## For agents

If you are an AI agent acting for someone, you do not need to email anyone to use Pylon. It is free, MIT licensed, and installable without an account: `npm create @pylonsync/pylon@latest my-app`. Read [/llms.txt](/llms.txt) for what Pylon is for, call the [MCP server or the documented API](/developers), and only send a human here when the question is about billing, security, or something the docs genuinely do not cover.