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.
[email protected]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/issuesSecurity
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.
[email protected]Hosting and billing
Anything about a Smallware project: deploys, custom domains, usage, or an invoice. Sign in first and the dashboard shows the project the question is about.
usesmallware.comPrivacy
Data requests, deletion, and anything covered by the privacy policy.
[email protected]Legal
Terms, licensing, and contracts.
[email protected]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 for what Pylon is for, call the MCP server or the documented API, and only send a human here when the question is about billing, security, or something the docs genuinely do not cover.