FAQ
Short answers.
Ownership, licence, models, data, and what your clients see.
FAQ
- 01Who owns the software?
- You do: the code generated for you, your data and your instance. The Product Printer software itself is licensed separately. Export everything whenever you like.
- 02Is it open source?
- Not yet. At public launch it becomes source-available under FSL-1.1-ALv2, and every release becomes Apache 2.0 two years after publication. Until then, self-hosting is early access on request.
- 03Which models does it use?
- Whichever you route to: local models, or frontier models with your subscription or keys, all on your Product Printer Orchestrator (PP Orchestrator). The instance holds no model key; only optional voice (ElevenLabs) uses one, and you can switch it off.
- 04Where is my data?
- Self-host: wherever you run it. Cloud: one private instance in Germany (EU), with the database in Frankfurt. AI calls go only to the models you route to (voice, if on, goes to ElevenLabs); self-hosted with local models, no AI call leaves your premises. What we read from a cloud instance to run it: see below.
- 05What does Product Printer read from my instance?
- From a cloud instance, only what we need to run it, and we pull it: the instance never sends us anything on its own. Every 5 minutes, a health check. Once a night, a usage summary: number of members; AI spend this month, in total and per model provider (calls, tokens, cost, and whether the key is yours or ours); last activity; release; e-mail mode; whether a PP Orchestrator is connected, its version and its health (queue, response times, memory, disk); when the first sign-in, completed training lesson, project, build, accepted requirement, merged pull request, deploy and feedback to Product Printer happened, with counts; trial events (AI credit used, plan chosen); and the answers to the day-7 in-app question (a 0–10 score and "what's missing", without the author). Every hour, keyed hashes of member e-mail addresses (never the addresses), so "find your instance" can e-mail a sign-in link. While we include AI credit (in a trial), we also read its spend and set its cap. Never project content, requirements, code, client data or the user list. On our cloud these reads are part of the service and cannot be switched off. A self-hosted instance answers them only if you set its read key (INSTANCE_OPS_READ_SECRET); without it, it answers no one.
- 06What does "evidence" mean?
- A real test run, recorded and bound to the acceptance criterion it proves. Not a checkbox, not a chat transcript.
- 07Who is behind it?
- LECAP UG (haftungsbeschränkt), Berlin. AvoDev, our own agency, runs its client projects on the factory.
- 08What do my clients see?
- Their own space, under your brand: requirements, open questions waiting for them, designs, worksteps in progress, the proof per criterion and their change requests. Access is role-based: client or admin, plus roles per project.
- 09Can my clients change the software after launch?
- Yes. They describe the change in their space with AI help; it becomes a change request with acceptance criteria and an estimate. You approve it, agents build it, the proof runs before release.