Straight answers aboutaccounts, keys, and code.

Azemax Studio is a browser-based AI code editor and development workspace. It combines a Monaco editing surface, a file tree and multi-tab workspace, an AI assistant that can inspect and change project files, code execution, and a diagnostics panel in one interface.

No. Azemax Studio runs in a modern desktop browser such as Chrome, Firefox, Safari, or Edge. There is no desktop package or command-line installer for the hosted product. You need an account, and an internet connection, because authentication, workspace sync, AI requests, and hosted code execution use online services.

No. The default Azemax mode sends AI requests through the Azemax backend, which uses the service’s own model configuration. Bring Your Own Key is optional: it lets you route requests to your own provider account and choose the model yourself.

Bring Your Own Key supports OpenAI, Anthropic, Google Gemini, OpenRouter, Groq, NVIDIA NIM, and any HTTPS endpoint that implements an OpenAI-compatible chat completions API. The settings panel offers a starter model list for each built-in provider and can fetch the provider’s model catalog when the provider supports it. Model availability and naming are controlled by the provider.

By default, a key is kept only in memory for the current browser tab and disappears when the tab closes. If you enable “Remember on this device,” the key is encrypted with a key derived from a passphrase you choose, and only the ciphertext is stored in the browser’s IndexedDB. In BYOK mode, requests go from your browser to the provider you selected, not through the Azemax AI backend. No browser-based storage can protect a key from malicious JavaScript running in an unlocked session, so use a restricted key and revoke it at the provider if it may have been exposed.

Yes. Agent and Edit modes can create, modify, rename, and delete files in the workspace as part of a task; they are not read-only chat. The assistant reports which files it touched, and edits are validated against the workspace before they are written. AI output can still be wrong, so review the changed files and test the result. There is no automatic Git commit or guaranteed undo for every file operation, so keep backups of important work.

Yes, through the Custom OpenAI-Compatible provider. Supply an HTTPS base URL and a model identifier, and the endpoint must accept OpenAI-style chat completion requests. Agent features that use tool calling require the endpoint to support tool or function calling. Endpoints that require client certificates, a VPN, or a browser extension are not supported.

The hosted execution service supports Python, JavaScript, TypeScript, C, C++, Java, Ruby, PHP, Perl, Rust, Go, Swift, Lua, Bash, C#, Scala, and R. Compilers and runtimes are provided by the sandbox service, so exact versions can change. Execution is intended for learning, experiments, and small programs; it is not a production CI runner.

Yes, depending on the features you use. Signed-in workspaces and settings sync through Firebase. AI prompts and the code context you include are sent to your selected AI provider (BYOK) or to the Azemax backend (default mode). Code you run is sent to the hosted execution sandbox. Azemax does not sell your content, and the Privacy Policy describes the categories of data involved and the providers used. Do not paste secrets or regulated data into a tool you do not trust.

Azemax Studio is in public beta and is currently offered free of charge; no payment card is collected by Azemax. If you use Bring Your Own Key, your AI provider bills your account directly under its own terms. No paid plans or future pricing are announced on this website, so do not treat the current beta arrangement as a permanent price commitment.

No. The hosted product needs a network connection for sign-in, workspace sync, AI requests, and code execution. The browser may cache static assets, but that does not make the workspace usable offline.

You can delete individual projects, files, and conversations in the workspace, and you can clear browser storage for the site. Full self-service account deletion is not implemented yet. To close an account and request deletion of server-side data, email azemaxhq@gmail.com from the address associated with the account with the subject “Account deletion”. Deletion is currently handled manually, and Firebase authentication records may need to be removed separately on request.