The questions skeptics ask us. Answered directly.

Yes, capsules run from your source code, and that instinct to protect it is exactly right; we'd be worried if you didn't ask. Here's the honest picture of what's changed: with modern AI tooling, the functionality of most software can be replicated from the outside in weeks, whether the code is shared or not. Secrecy protects less than it used to.

What can't be replicated is a product that's continuously improving from real customer usage. That's what the platform gives you: symbiotic development means your product grows from every edge case and every piece of feedback, automatically. Your protection stops being secrecy and becomes momentum no one can catch up to. And on the code itself, we've built specific safeguards, covered in the next question.

We'd rather you hear this from us than find it in a contract later. Inscendo owns the capsule code built on the platform, and licenses it back to you on terms designed to be the practical equivalent of ownership: perpetual, worldwide, royalty-free, and transferable, covering your right to run, copy, modify, export, distribute and commercialize that code on or off the Service. It survives if you leave. That is the same rule for every publisher on the marketplace; no publisher and no installer owns platform code.

Two things follow from that, and they're the reason we say it plainly. The licence can be revoked for cause, meaning infringement, illegality, or an acceptable-use breach, and it doesn't grant any right to use our trademarks. Because much of this code is AI-generated, and copyright in AI-generated material may be limited or unavailable to anyone under current U.S. law, the rights on all sides are primarily contractual rather than a matter of authorship. And publishing is not confidential: a published capsule and its source are expressly not your Confidential Information, we owe you no non-disclosure or trade-secret obligation over them, and you waive trade-secret claims against us and against installers acting within their licence. We would rather you weigh that up front than discover it later. The protection here is deliberately not built on code secrecy; it is built on licence limits, publish-time screening, price integrity, and your brand.

The full terms are in the Marketplace Publisher Agreement and the Master Subscription Agreement, and we're happy to walk your counsel through them.

Protecting your revenue is part of our job, not just yours, and it's built into the platform at three levels:

1. Screening at publish time. Every capsule submitted to the marketplace is compared against the existing listings before it goes live, using provenance and commit-history analysis alongside source similarity. A capsule the platform can tie to another listing it was installed from is refused outright. Similarity and provenance findings do not block a publish; they raise a flag for our review. These measures are best-effort, we don't warrant they catch every violation, and we don't take on an obligation to police the marketplace.

2. Exported code loses its power. Even if someone exported your capsule's code, they'd have to recreate the entire Inscendo platform for it to work as intended. Stripped of Inscendo IQ and the platform's capabilities, it becomes ordinary software: a massive downgrade from what your customers actually pay for.

3. Provenance tracking. Our version history works like a blockchain: every capsule carries a trace of the work that produced it. If someone copies code, modifies it locally, and re-uploads a large codebase with no trace of that work, it's automatically flagged as suspicious.

And it's worth being honest about the baseline: without a patent, and even patents are famously finicky and don't always hold up in court, there's realistically little anyone can do about copying out in the open market today. Publishing with us means that, at a minimum, there is something actively working against it here rather than nothing, though as above we don't warrant it catches every case. Your protection is structurally our interest: the marketplace only thrives if partners know their code is safe here.

No, because clients never touch your capsule. Every customization happens inside that client's own version of the capsule, within your intended design, so the canonical capsule you built stays exactly as you designed it, for every other customer, always.

It gets better: the differences each client creates in their own version flow back to you as feedback and recommendations for improving your capsule. You see what your customers actually need, and you decide what to adopt. They get a perfect fit; you keep the relationship, the design integrity, and the revenue.

Your product represents years of thinking, and that deserves protection. What we'd gently offer: the deepest advantage in your product was never the code itself. It's your understanding of the customer problem, baked into every design decision, and that's the thing no one can copy. AI can now build years' worth of code in minutes, which is exactly why the strongest place for your advantage to live is somewhere code can't be copied from: momentum, customer insight, and a product that compounds.

That expertise is what the platform amplifies: distribution to buyers, a continuous stream of real-usage insight, and a product that grows itself while your team focuses on the vision.

Every one of your customers gets Inscendo IQ included. It operates your capsule and automates further with custom agents, safely customizes it to each client's needs inside their own version, self-diagnoses issues in the capsule, and answers your customers' how-to questions directly.

Here's the framing we believe in: without an AI operating it, every piece of software ever built is just another tool a human has to manually use for it to be effective. On our platform, your software becomes a living asset that operates the tool. That capability comes standard, for every customer, from day one.

The moment your code runs as a capsule, it starts capturing edge cases, bugs, gaps, and every other kind of feedback from real usage, and sends it right back to you to improve the capsule further. The platform organically grows your product to fit what people actually need, across every edge case, instead of you having to constantly develop it yourself on assumptions.

The question we'd pose back: would you rather your software be manually developed, or grown to constantly fit what your customers need? More detail is on our Symbiotic Development page.

This concern is genuinely real right now, while the broader business world is still catching up on how to use AI and deciding whether to jump on board. We won't wave it away. But that transition is also the opportunity: once you've shown your clients the value of what IQ can do, they will pay you well for your services to help them build what they don't yet understand.

And the platform itself shortens that learning gap: your customers don't learn the platform, Inscendo IQ learns them. It answers their usage questions, walks them through the capsule, and tailors it to their needs. It turns your clients into self-helpers, the onboarding and training burden you carry today largely disappears, and customers feel more supported, not less.

Your integration work is real value, and it carries over; this isn't about replacing it. What capsule connectivity adds is context. Traditional integrations move data between systems. Inside InscendoIQ, Inscendo IQ actually understands each client's environment: their other capsules, their processes, their legal constraints, their operations, and it operates your product in concert with all of it.

And because of everything it's exposed to in that symbiotic environment, it can even surface revenue opportunities and leaks you couldn't otherwise catch. Your product goes from being connected to being aware, which is what makes it feel indispensable inside a client's stack rather than just another standalone app.

Four compounding returns: continuous product insight, every edge case, bug, and feature gap from real usage routed straight to you; tier-one support, since Inscendo IQ self-diagnoses capsule issues and answers your customers' how-to questions; little to no infrastructure and scaling costs, since we handle those at the platform level; and distribution through a policed marketplace where your revenue is better protected than any channel leaves it.

For most partners, those are four separate line items right now. We're always glad to map them against your current spend so you can see the real number for your business rather than take our word for it.

We'd expect nothing less than that question. Security is one of the burdens we carry so you don't have to carry it alone: infrastructure, monitoring, and platform-level protection are our responsibility, not something every partner has to solve individually.

Our practices are documented on our Security page, and we're happy to go through them line by line with your technical team.

Exactly the right question to ask any platform partner, and one that deserves specifics rather than slogans, so we answer it in detail with your technical team as part of any evaluation. What we can say here: one of the reasons partners choose the platform is consolidation. Most companies' data today is spread across a dozen disconnected tools, each with its own security posture. On InscendoIQ it lives in one governed environment with one accountable security model, and one partner you can hold responsible.

Reach out and we'll set up a session with your technical team to walk through data handling in depth.

That caution is healthy: an ungoverned AI with system access would be dangerous, and we built Inscendo IQ specifically so no one has to accept that risk. It operates with defined permissions, inside capsule design guardrails, with full accountability.

Worth considering too: your people, and your customers' people, are almost certainly already using AI tools on their own. One governed, visible, permissioned AI is how organizations get ahead of that. It replaces shadow AI with something you can actually oversee.

Totally fair. The difference comes down to context. Inscendo IQ isn't a chatbot guessing from general knowledge; it operates your capsule with the actual source code, your documentation, and the client's environment in view. That grounding is what makes it reliable, and it's the difference between a party trick and a true operator.

And when something does slip through, the symbiotic loop catches it and routes it straight back to you as a fix, so quality improves continuously instead of eroding. We're glad to show it operating a real capsule live, so you can judge the reliability with your own eyes rather than our assurances.

It's a fair question, and honestly the skepticism is earned. Most AI tools disappoint for the same reason: they're bolted on with no context. They can't see your data, your systems, your processes, or your other tools, so they produce generic output. Inscendo IQ lives inside the environment; it sees your capsule, the client's other systems, and the company's actual operations.

Context is usually the whole difference, and it's also where the upside comes from: because of everything IQ is exposed to, it can surface revenue opportunities and leaks you couldn't otherwise catch. If you're open to sharing what fell short last time, it tells us exactly what to demonstrate for you, and we'd genuinely like to know.

That's the question every software company should be asking right now, and it deserves an honest answer: AI is going to pressure products that stand still. That's precisely why the platform is built the way it is. On InscendoIQ, your product never stands still; it grows continuously from real customer usage, faster than any roadmap could keep up manually.

There's a second layer of protection too: customers who might otherwise use AI to build their own version of your product, treating you like a middleman, instead get safe customization inside your capsule. The build-it-themselves temptation gets absorbed into your product rather than aimed at it.

Waiting has been the smart move for a lot of the AI products out there; plenty are thin wrappers. What we'd share from our side of the table: the pattern we see is customers using AI to decide whether they even need to buy software anymore, or whether to build it themselves. That shift is happening with or without any of us.

The platform exists so developers benefit from that shift instead of getting squeezed by it, and because symbiotic development compounds month over month, the partners who start earliest build the biggest head start. We're glad to help you evaluate the timing honestly, including whether now is right for you.

Yes. Customizations live in each client's own version of your capsule, layered on top of the canonical capsule you publish, so access always runs through your marketplace subscription. Your recurring revenue continues no matter how tailored a client's version becomes, and the platform actively polices attempts to circumvent capsule fees.

To set expectations first: automation runs are billed at a single flat rate today, and marketplace capsules are not yet cheaper to run than anything else. Preferential marketplace pricing is something we are engineering, not something live right now.

The intent behind it is partner protection. When automations get built from scratch and used improperly, things break, and the fallout tends to land on the developer whose software was involved, fairly or not. Pricing marketplace capsules lower would steer clients toward professionally developed, tested automations: yours.

That isn't devaluing custom work; it's making the safe, high-quality path the easy path, which protects your brand and your customers at the same time.

Completely understandable; nobody needs another line item this year. The honest way to look at it: the platform absorbs several costs you're likely carrying already, including hosting and infrastructure, security tooling, support hours, QA cycles, and integration development, and it adds a revenue channel on top. For a lot of partners it nets out as consolidation, not addition.

But that's an empirical question about your business, not ours to assert. We'd rather run the math with you on your real numbers, and if it doesn't genuinely pencil out, we'll be the first to say so.

Smart thing to pressure-test before trusting any channel; we'd ask the same. Our full fee structure and terms are part of every partner conversation, in writing, so you can see exactly where you stand before committing anything.

Beyond the terms themselves, two things. First, our incentives are aligned in a way most channels aren't: we actively police fee circumvention to protect your recurring revenue, because if partners get burned, the marketplace dies. Second, we hold ourselves to a standard: any increase in fees should come with an increase in the technology, the support, and ultimately the value the platform provides.

You know your product's depth better than anyone, so we take this seriously rather than wave it away. What we've found is that complexity is usually where the platform helps most: complex products carry the heaviest support load, the most edge cases, and the hardest integration questions, and those are exactly what the platform takes on through self-diagnosis, continuous feedback capture, and native connectivity. For products with real depth, the highest level of intelligence we offer is also available in the Premium subscription of Inscendo IQ, built for exactly this kind of work.

Rather than claim that in the abstract, we'd rather look at your architecture together. We'll scope your product specifically, with no commitment, and give you an honest read on the fit, including if the answer is "not yet."

This is exactly the practical detail worth getting concrete on, and the full release workflow is something our technical team walks through with yours as part of any evaluation, so your engineers can pressure-test it directly.

The bigger shift worth knowing about now: the symbiotic loop means you'll be versioning based on live signal from actual usage rather than assumptions. Roadmap guesswork is often the most expensive part of development. That largely goes away here.

That dependence is exactly why we take reliability as seriously as we do; your customers become our responsibility too, and we don't take that lightly. Platform-level infrastructure means reliability engineering is a full-time, well-resourced discipline here, rather than something each developer shoulders alone at 2 a.m.

We'd rather show you the specifics than ask you to trust the sentiment. Our uptime track record, monitoring and incident process are all part of the partner evaluation, and we'll put them in writing. To be straight with you: we do not publish a contractual uptime SLA today, and the Master Subscription Agreement is written on an as-is basis. If a committed service level is a requirement for you, raise it during the evaluation and we'll talk about what we can commit to in your agreement.

We respect that a lot, and it's worth being precise about what changes and what doesn't. Your product, your pricing, your roadmap: still yours, fully. What you hand off is the load that has nothing to do with your vision: infrastructure, security, support tickets, and the guesswork about what customers want.

Operational load is usually what erodes a founder's independence day to day. We think of the platform as keeping the control that matters and shedding the burden that doesn't.

We'd rather have your skepticism than your blind faith. So don't evaluate the claims in the abstract: pick one workflow, run it as a capsule, and measure the results yourself. Feedback volume, support deflection, customer response, all with your own numbers.

If it doesn't hold up, you've lost very little. If it does, you'll have seen it with your own eyes. The platform makes falsifiable claims on purpose; test them.

That's prudent, and we won't pretend early adoption carries zero risk. Here's what we'd want you to weigh alongside it: symbiotic development compounds. Every month on the platform, a capsule captures edge cases and grows to fit customer needs, so early partners don't just get in first; they build a product lead that later entrants have to chase.

There are low-commitment ways to start that don't require betting the company, and we're glad to shape one around your risk tolerance.

This is a real decision and it should involve your team, so here's what we suggest. Send each audience the material written for them: founders usually start with our Vendors page, engineering leads with Symbiotic Development, and business stakeholders with the Platform overview, so nobody's reacting to a secondhand summary.

And if it would help, we're glad to join that internal conversation and take the hard questions directly. The first one is usually about source code, and as you've seen above, it's the one we most like answering.

Then we'll tell you, plainly, and part as friends. We only want partners who genuinely win on the platform; a partner who joins reluctantly and churns helps no one, least of all their customers. If a scoping session or pilot shows the fit isn't there, you'll hear it from us first, along with our honest read on what would need to change.