Builder Rules

These are the limits that apply to every builder. Each one traces to an accepted decision or to how the product works today.

Do

Set your own prices on your own listings, at $10 or more when you charge (dec-013).
Describe your automation accurately: tools, scope, exclusions and what the buyer must connect.
Name real tools in your listing so request matching is honest.
Keep your client relationship and use your own tools (dec-016).
Send a client's changes to the client for review before they are made.

Do not run a reseller or wholesale program. SchemaBounce sells its platform on one set of plans. If you serve clients, you do it as a builder, and each client's workspace and data belong to the client (dec-015).
Do not hide the platform. There is no white-label. The certification mark stays co-branded beside your name (dec-014).
Do not promise leads or volume. The marketplace does not guarantee buyers, requests or income. Opportunities depend on what businesses post. Do not claim otherwise in a listing or a proposal.
Do not put credentials in listings. No API keys, tokens or passwords in manifests, notes, summaries or fixtures. The importer removes credentials from n8n exports, and you still check what you paste.
Do not publish someone else's work. A manifest byte-identical to another publisher's is rejected. Paid listings do not permit derivation.
Do not redistribute or resell what you buy. The listing license lets a buyer run what they bought.

Buyer requests belong to builders and are not used to sell SchemaBounce's automations or services. Raw request text is deleted 30 days after the request closes (dec-009).
Notifications carry ids, counts, stages and timestamps only. Email is transactional only (dec-085).