FAQ

PAULGA is a desktop platform that connects architectural AI work. It keeps document search, AI rendering, and CAD execution in one workflow.

No. Your CAD remains the execution surface. PAULGA assists search, rendering, and repetitive CAD actions around the tools you already use.

No. PAULGA speeds up judgment and draft work. Drawings, codes, quantities, and client-facing deliverables still need review by the architect or office.

When an AI capability matters to architectural practice, we work to bring it into the product. Our target is at least one meaningful platform addition every three months.

PAULGA is built around Revit, Rhino, AutoCAD, and SketchUp. Capability depth varies by platform and continues to expand.

No. Revit LT does not expose the plugin APIs needed for this workflow. Use the full Revit application to connect PAULGA.

The current desktop and CAD connection flow is built for Windows. macOS support will be reviewed as platform support expands.

Yes. Install PAULGA Desktop and the CAD plugin, then close and reopen the CAD software. The plugin loads cleanly in the new session.

Yes. After signup and email verification, you receive 7 free days and 1,500 onboarding credits. You can start a paid plan when you need more usage.

Credit usage depends on the task, model, input size, render options, and whether reference images are used. Credits measure usage, not feature locks.

Solo fits individual practice. Pro fits repeated project work. Studio fits teams that use rendering and CAD execution often.

Monthly Work Credits reset each month. Purchased Work Credits stay in a separate wallet and expire 12 months after payment.

No. The default CAD connection between Desktop and the plugin happens on your own machine. It is not designed to open CAD access to outside networks.

PAULGA does not sell customer work as training data. Features that call external AI APIs follow the provider policy, and sensitive projects may require a dedicated configuration.

Only the context needed for the requested feature is sent. This can include your prompt, active view metadata, selection state, and documents or images you provide.

It depends on the contract. If the project restricts cross-border transfer or approved vendors, review those terms before using the standard plan.

The default plans are built for individual and small-scale use. Team billing, user management, and shared credits can be scoped separately.

Ask your IT team to allow the PAULGA executable and required service domains. If it is still blocked, send the install log and security environment details to support.

The standard plan needs internet access for accounts, billing, and AI API calls. Fully offline deployment requires a separate enterprise design.

Do not assume the standard plan fits those projects. Data location, provider contracts, logs, and internal network rules need to be reviewed first.