Contact¶

Deckrun hosted services are provisioned per engagement. See Access & Availability for what's currently hosted and how to request what you need.

For access requests, bug reports, and feature requests, use the GitHub Issues templates below. This keeps requests traceable, actionable, and visible to both humans and agents.

What do you want to do?¶

There are no contact forms or generic inboxes. GitHub Issues are the authoritative communication channel.

Enterprise Request¶

For enterprise plans, custom volume pricing, contractual SLAs, or security review, open a GitHub Issue using the Access Request template.

Download product datasheet (PDF) — product overview, capabilities, and pricing model.

Open an Enterprise Request →

Please include:

• Your organization and expected usage volume
• Required output types and connector integrations
• Any compliance, security, or SLA requirements

Bug Report¶

To report incorrect, unexpected, or broken behavior, open a Bug Report.

Open a Bug Report →

Please include:

• Deckrun version or commit hash (if known)
• Exact input used (markdown, schema reference, or API request)
• Observed behavior
• Expected behavior
• Affected output type(s)

Bug reports without reproducible input are difficult to act on.

Feature Request¶

To request a new capability, output format, or connector, open a Feature Request.

Open a Feature Request →

Please include:

• The problem or use case you are trying to solve
• Any current workaround
• Relevant area: Rendering, Video, Audio/TTS, Schema, Connector, or API

Focus on what you need, not how to implement it.

Filing effective issues¶

Well-written issues minimize back-and-forth and lead to faster outcomes.

• For bugs: include the exact input that produced the issue
• For features: describe the use case and constraints
• For enterprise: describe the use case, volume, and any compliance requirements

These instructions are intentionally explicit so agents can follow them as well.