We use essential cookies to run this site and remember this choice. With your permission we would also use analytics cookies to see which pages help visitors. Analytics is not switched on yet; your choice applies if it is. Cookie details.
In early development. Condense is in early development. Design partners shape the first version. Read more
Design partner program
We are working with a small group of software teams to understand how commerce backends are built today and define the first Condense integration around real development needs.
Apply to Become a Design PartnerCurrent stage
Condense is in concept and early validation. There is no production API or public sandbox yet. Partners help define the first version: the API contract, the workflows, and what is worth building first.
01. Who should apply
Participation does not guarantee access to a working API, funding, compensation, or specific commercial terms.
Questions
Condense is an API-first commerce infrastructure product being developed by Unfazed. The goal is a reusable backend foundation for product catalogs, inventory, and orders that software teams can integrate into the client applications they build.
Software agencies and development teams that deliver commerce functionality for clients and find themselves rebuilding similar backend capabilities from project to project.
Those projects often connect sellers, who own products and stock, with resellers, who sell them. Condense is designed so a seller can share stock with many resellers, a reseller can sell from many sellers, and stock and orders stay in sync between them.
Product records, inventory levels and adjustments, and order creation and management, exposed through a developer-facing API. The exact contract is still being defined with design partners.
Not yet. There is no public API, sandbox, or self-serve access today. The examples on this site describe a proposed contract. Design partners help review that contract and will be invited to test integrations as functionality becomes available.
Conversations about a real commerce project you have delivered or are planning, sharing the workflows and constraints you work with, and reviewing the proposed API. When the relevant functionality exists, it also means testing a practical integration and giving feedback on the developer experience.
Participation does not guarantee access to a working API, compensation, or specific commercial terms.
No. Condense is not intended to replace every ecommerce platform, payment provider, ERP, or logistics system. Part of the validation work is understanding which projects a shared commerce layer suits, and which are better served by what teams already use.
No. Payment processing is not part of the initial scope. Orders are designed to carry their own status, kept separate from payment, so teams can continue to use the payment provider their project requires.
That is the intent. Access is planned as a rule you set per reseller and per product: a reseller you have not approved cannot see or sell your stock, and removing access is designed to take effect for new orders immediately. The exact controls are being defined with design partners.
Every seller that grants you access appears through the same API, in the same resource shapes, so adding a seller is designed to need no new integration work. No limit has been defined yet; the first version is being scoped with design partners.
Apply through the design-partner form. Tell us about your team and a current or planned commerce project, and we will follow up if there is a good fit for this early stage.
02. Application