// faq
Clear answers before you request access.
What Praxys does in builder preview, what still needs to be confirmed project by project, and where automation ends and your engineering judgment begins.
-
What is Praxys?
Praxys is a builder-preview platform for turning a product brief into a working application. Its compiler coordinates frontend, backend, data-model, migration, and deployment changes so you can review a coherent change instead of stitching together a demo by hand.
-
Who can use Praxys today?
Praxys is not a public self-serve product yet. We are working with a limited set of builders in preview, so access, supported workflows, and hosting arrangements are agreed directly with each participant.
-
What does Praxys generate?
A requested change can span the user interface, server behavior, schemas, migrations, tests, and deployment configuration. The exact output depends on the project and the approved scope; Praxys is meant to produce reviewable changes, not to promise that every prompt is safe to deploy unchanged.
-
How is generated work checked?
Praxys has automated checks for things such as generated-code structure, TypeScript types, adapter conformance, and application booting. The checks used depend on the project and environment. They reduce avoidable failures, but they do not replace a developer's review, testing, or responsibility for the finished product.
-
Can I edit the code myself?
Yes. Praxys is designed around reviewable project changes rather than an opaque visual-only editor. Preview participants should confirm the repository, export, and collaboration setup for their engagement before relying on a particular workflow.
-
Does Praxys support multi-tenant apps?
The platform has distinct single-tenant and multi-tenant application models, including tenant-aware generation and data-access controls. Multi-tenant hosting is still a controlled preview capability, so do not assume it is available for every project or that it removes the need to review your own authorization rules.
-
What integrations are available?
Praxys has a substrate of typed backend contracts and provider adapters across areas such as data, payments, messaging, identity, storage, and AI. An adapter existing in the catalog does not guarantee that it is enabled, production-ready, or appropriate for your project; we confirm the supported provider and its configuration during preview.
-
Where do apps run?
Praxys includes runtime and hosting work with microVM-based isolation paths. Managed hosting is not a generally available service today. For a preview project, we will be specific about the environment, deployment path, isolation boundary, and any operational limits before you depend on it.
-
Can I self-host or bring my own cloud?
Those are not public, self-serve options today. The platform has deployment abstractions and self-hosting work in progress, but availability and support need to be confirmed for each preview engagement.
-
What security guarantees does Praxys make?
Praxys is building controls such as tenant-scoped access, managed egress policies, separate secret handling, and audit trails. Those controls are not a security certification or a substitute for application security. You remain responsible for your authorization rules, data handling, integrations, and review process.
-
What does Praxys cost?
There is no public price list while Praxys is in builder preview. If there is a fit, we will discuss scope, support, and commercial terms directly before work begins.
-
How do I request access?
Send your email through the request-access form and tell us what you are building. We will contact you if there is a fit for the current preview; a request does not guarantee access or a launch date.
Still have a question?
Join the waitlist and tell us what you are building. We will be in touch if there is a fit for the current preview.