Dream Maker holds what your team knows about its own systems. We design for that from the start rather than adding controls afterward.
Every project runs in its own space with its own keys. One project's agents have no path to another project's memory, and this is enforced by the architecture rather than by a permission setting that could be misconfigured.
The systems that handle accounts, plans and billing are separate from the systems that hold your memory. Billing can see that a space exists and what it costs to run. It cannot read anything inside it.
Model provider keys are deposited write-only. We record a fingerprint so you can confirm which key is in use, hand the value to your project's process when it starts, and keep no readable copy. Nobody, including us, can read a deposited key back.
Every action taken by an agent or a person is recorded with what it was based on. Audit records are exportable at any time. On the Enterprise plan you can stream them into your own logging system.
If your policies require that code and knowledge never leave your infrastructure, Dream Maker runs entirely inside your own cloud. In that configuration we have no access to your data of any kind.
Send details to [email protected]. We acknowledge reports within one business day and will keep you updated through to a fix. We do not pursue legal action against researchers who report in good faith and give us reasonable time to respond.
We are happy to work through review questionnaires and architecture reviews. Get in touch and we will connect you with an engineer.
Dream Maker reads your project and proposes the goals it finds there. You approve the direction, and your fleet is working within the hour.