Naia Build Frequently Asked Questions (FAQ)

Yes. Naia Build is available by default using the Google Gemini foundational model, which requires no API key configuration and is provided by Neptune. A Claude API key is required only if your organization chooses to use the Claude model for enhanced output quality.

The customer is solely responsible for all costs associated with their Claude API key. Neptune proxies requests to Anthropic but does not manage billing or assume responsibility for usage costs. Cost limits can be set at account and user level in the Neptune DXP Portal to support organizational cost control.

Yes, it matters for cost accountability and spend limits. Selecting your personal account means requests are billed against your personal Claude API key and governed by the daily spend limit you set at the personal account level. Selecting your organization account means requests are billed against the organization’s key and governed by the limit the administrator configured for that account. The two keys and their limits are entirely independent. If your organization has set a restrictive daily spend limit you expect to exhaust, or if you want to keep personal usage costs separate from your team’s, the choice has direct billing consequences. When uncertain, confirm with your administrator which key your team is expected to use before starting a session.

Saving the organization API key is a prerequisite but not sufficient on its own. For an organization account, user-level authorization is a separate step. After saving the key, an administrator must explicitly enable each user by toggling the switch next to their name and saving again. A user who was not enabled at that point, or who was added to the organization after initial setup, will not have access even though the key itself is active. If no users appear in the list, the administrator should use Sync Users to pull in the current user list before enabling individuals. The user should also confirm they are signing into Naia Build with their organization account credentials, not their personal account, since authorization is account-specific.

Switching keys changes the billing source and applicable spend limit for subsequent requests, but does not discard application components already generated. These are saved in the Neptune DXP - Open Edition environment continuously. However, switching accounts may reset or interrupt the conversational history that Naia Build uses to maintain awareness of prior prompts and changes. If you are mid-way through a complex generation sequence, it is advisable to reach a stable checkpoint before switching keys, rather than doing so during an active generation or multi-step workflow, to avoid losing the contextual continuity that informs subsequent prompts.

Naia Build requires an active WebSocket connection to process prompts. Application components generated up to the point of disconnection are saved within the Neptune DXP environment and are not affected. In-session context and conversation history are not recoverable after a connection loss ends the session.

Application components generated during the session are saved in the Neptune DXP environment and persist beyond the session. Conversation history, in-session context, and any source code retrieved during the session are discarded from volatile memory when the session ends and are not recoverable.

Source code is not transmitted as a matter of course. Application structure metadata, for example, component counts, page names, and model names, is included in every request. Individual source code fragments are retrieved and transmitted only when the AI explicitly requires a specific component to complete a task. Bulk source code is never collected, stored, or transmitted. See Security and data for a full breakdown.

No. Each session is scoped to a single application. Naia Build has no knowledge of other applications in the environment. Data structures from another application must be exposed through an API explicitly added to the current application’s Data tab before Naia Build can reference them.

Yes. Naia Build and the Neptune DXP - Open Edition App Designer low-code environment are accessible within the same workspace. The Code tab provides full access to the component application tree and Settings/properties pane at any point during development. Switching between the two modes does not affect application state. Naia retains awareness of manual changes made in the App Designer when generation resumes.

Naia Build is an application development tool. It generates UI, logic, and data integrations within the Neptune DXP - Open Edition App Designer. Naia Agent Studio is the framework for configuring and maintaining AI agent logic, and belongs to the Naia for Business feature set. The two products intersect when an application incorporates AI agents: Naia Build manages their UI placement and API connectivity, while their underlying logic is configured in Naia Agent Studio.

No. Naia Build generates and refines application components within the Neptune DXP environment. Deployment to a launchpad, server script configuration, and platform infrastructure setup are outside its scope and are handled through standard Neptune DXP processes.