Professional work around an open core
Priority support and tailored QZX work
Organizations and teams can request scoped priority support, compatibility validation, Result Contract interoperability pilots, sponsored development, or a QZX adaptation for a specific environment. QZX Core remains free and open source.
Start a 2-minute briefAvailability, response targets, deliverables, price, and publication boundaries are agreed in writing before work begins.
QZX Professional Services
Tell us what outcome you need
Start with only the essentials: request type, your name, work email, and the outcome you want. Technical context, timing, budget, and confidentiality are optional and can be discussed later. You will receive a reference for follow-up.
Prefer email? Contact Alejandro Sánchez, QZX's creator.
qzx@yumbale.comDescribe the result you need, without passwords or other secrets. Include your request reference if you already received one.
Priority support
Reserve focused technical attention
Agree on a first-response target for triage, reproduction, upgrade planning, and technical guidance. Payment reserves time and accountability; it does not guarantee a fix, a favorable finding, or 24/7 availability.
Compatibility
Validate an exact environment
Request testing or adaptation for a particular Windows, Linux, or macOS release, Python version, terminal, browser, architecture, agent, or policy. The proposal identifies the matrix and any access, hardware, or licenses needed.
Interoperability pilot
Test QZX Result Contract v1 in a real workflow
Define a bounded pilot for a CLI, MCP server, agent platform, or internal automation tool. For structured-output MCP producers on 2025-06-18, 2025-11-25, or 2026-07-28, the pilot can map QZX Result Contract to outputSchema and structuredContent, record the schema-strength mode, verify completed success/failure consistency with isError, and publish a reviewable conformance report, deviations, reusable validators, and limitations without purchasing endorsement or control of the open specification.
Sponsored development
Scope a feature or integration
Propose a QZX feature, integration, or modification with a concrete outcome. Reusable improvements are intended for the open project under Apache-2.0; client data, credentials, and genuinely specific materials remain protected.
What happens after you send the brief
-
1. Brief
Describe the useful result
Include the operating system and exact version, QZX and Python versions, impact, desired evidence, deadline, and any confidentiality constraints.
-
2. Feasibility
Confirm fit and capacity
Alejandro reviews technical fit, available time, dependencies, risks, and whether a smaller discovery or reproduction step should come first.
-
3. Written scope
Agree before committing
The proposal states deliverables, response target, price, payment terms, acceptance evidence, confidentiality, and which improvements can be published.
-
4. Delivery
Produce evidence, not promises
The work is tested against the agreed environment and reported with results, limitations, and next steps. General improvements strengthen the open core whenever applicable.
A service agreement is not a donation
Donations support general maintenance without purchasing priority or deliverables. Professional services create a separate, scoped agreement. Essential security work is prioritized by risk, and no customer receives control of the general roadmap, private user telemetry, or a guaranteed favorable compatibility result.
Requests may be accepted, narrowed, scheduled, or declined according to capacity, feasibility, safety, and alignment with QZX.