Understand the systembefore you build with it.

Aetherion AI is a project-aware AI IDE with an integrated cloud. It brings planning, generation, files, code editing, live preview, diagnostics, versions and publishing into one workspace.

No. It can begin with a landing page, but the workspace is designed for multi-page websites, SaaS products, dashboards, customer portals, internal systems and automation interfaces that continue evolving after the first generation.

Aetherion is for founders, freelancers, product teams and business operators who want to turn requirements into working software without assembling a separate AI tool, code editor, preview environment and deployment stack.

No. You can work through briefs, conversation and visual preview. Developers can go deeper by opening the files, editing code, reviewing structure and exporting the project.

Your project remains a real file-based workspace rather than a locked screenshot. You can continue editing it in Aetherion and use the available export or publishing options under your plan and the platform terms.

You can describe an idea from scratch, choose System DNA to guide structure and visual behavior, or open a Ready Template as a complete starting point. Each path ends in the same editable AI IDE.

System DNA is a reusable set of structural and visual decisions. It guides how Aetherion composes a new product without forcing you to begin from an already finished page.

A Ready Template is an existing full-page or multi-page project that can be previewed, opened and remixed. After import it becomes your own editable workspace rather than a fixed demo.

Aetherion works with project context such as the brief, files, selected assets, routes, previous decisions and runtime state. The exact context used depends on the operation, so focused changes do not need to regenerate everything.

Yes. The IDE exposes the project tree and individual files, allowing precise edits alongside conversational changes and live preview.

The workspace is designed to preserve the useful result, surface the problem and offer inspection or repair flows. Runtime Doctor and Fixer can diagnose and correct issues without requiring a complete rebuild.

Yes. Projects can use uploaded assets and AI-generated images. Available providers, models, automatic images per build and media capabilities depend on the active plan and platform configuration.

Aetherion Cloud is the managed release layer connected to the IDE. It handles public previews, publishing, deployment history, project status and domain operations from the same workspace.

Preview lets you inspect a project while it is still being built. Publishing creates a live release that can be shared and operated independently from the current editor state.

Yes. A published project can use a custom domain where the plan and project configuration allow it. Aetherion shows the required domain state and connection status inside the Cloud workspace.

Projects keep file versions, snapshots and deployment history where available. These checkpoints provide a controlled route back when a later change is not the version you want to keep.

Where export is enabled, Aetherion can package the selected deploy files and project assets as a ZIP for external review, development or hosting.

Aetherion includes repository connection workflows for supported providers. The exact Git actions available depend on the current integration state and your workspace permissions.

Yes. New accounts can begin on the active Free plan and receive the signup credits configured in Aetherion Billing. No paid subscription is required to create the account.

A plan controls project capacity, active projects, publishing, storage, recurring credits, generation limits, available AI workflows and support level. The public Pricing page reads the current active values from Admin Billing.

A credit is the platform unit used to account for AI and media work. Opening a project or editing ordinary workspace data does not consume credits; generation and advanced model operations can.

Generation workflows are designed to show an estimate before work begins. The final charge is recorded with the operation, so usage and balance changes remain visible in Billing Activity.

A completed generation is preserved. If its settled cost is greater than the available balance, Aetherion records the outstanding credit amount instead of running the AI operation a second time. Added credits can settle that amount and resume waiting work.

Plans that allow credit purchases can add an active credit package from the workspace. Packages extend AI usage without changing the project and publishing limits of the subscription.

Yes. Plan changes, cancellation state, renewal dates, invoices and the customer billing portal are available through the account billing area. Some changes apply immediately and others at the next billing period, as shown before confirmation.

No. A project stays inside your authenticated workspace until you deliberately create a public preview or publish a release.

Access is tied to authenticated accounts and the roles supported by the platform. Public project releases are separate from private editor and account data.

Aetherion can route work to configured AI and media providers. The provider and model available for an operation depend on platform configuration, plan access and any user-controlled provider settings.

Project deletion includes cleanup workflows for project data, stored assets and managed deployments. Account-level requests are handled through account settings or support, subject to legal and billing retention requirements.

The public Privacy Policy, Terms of Service, Cookie settings, Security Center and Data Processing Addendum describe the current platform rules in more detail.