Altifigence Cloud
Sign in to Altifigence Cloud and see the projects and services available to your account.
In Cloud, opening a project, editing, saving and viewing stored results do not wait for a personal runtime to start. Opening a project does not itself submit a managed engine job; supported PC calculations and server jobs have separate availability. Existing active writers remain protected. See Projects, Jobs, and Runners for current execution hosts, storage limits and job availability.
Overview
Altifigence Cloud is the signed-in customer console. It complements the released local applications; it is not required for every local edit or local engine operation.
What You Can Open
Surface | Purpose | Availability |
|---|---|---|
Altifigence account | Browser identity and account session | Used by the website, Cloud Console, and desktop authorization flows |
Public Downloads | Released installers and verification files | Verified installers and verification files are public; website sign-in is not required |
Windows My PC | Edit and save without sign-in; protected local features require sign-in | No device licence in 2.0.2; Free sign-in is sufficient for the documented local features |
Cloud Console | Account and enabled organization, project, usage, or service views | Visible features depend on the account |
Developer access | Typed native CLI and authorized MCP connections | Use the documented interface and its current project/tool permissions |
Verified installers are available without website sign-in. Paid features, organization roles, usage balances, and API access are checked separately when you use those services.
Local Projects and Online Actions
Opening the Cloud Console does not upload a local workspace. Digital Design Studio (including ISA workflows) and local CLI tools keep their documented local data boundary until you explicitly select an action that transfers source or artifacts.
Before starting an online action, review the organization, project, files being sent, execution location, expected output, and any usage or credit shown in the interface.
Sign-In
Opening https://cloud.altifigence.com/ redirects a signed-out browser to the Altifigence account service and returns to the console after authorization. Desktop applications use their own local sign-in callback and host-specific capability checks; see First Launch and Account Access.
Service Availability
The console shows the projects, runners, jobs, artifacts, credits, usage, and billing features enabled for the signed-in account. If a feature is missing, check the account and project or contact support.
Open your first project
Sign in at Altifigence Cloud and confirm the selected organization.
Choose a project you can access. If it is missing, check the organization and membership before creating a duplicate.
Open DDS, then choose the intended RTL or ALcad workspace. Read a runtime state only for an operation that actually uses that runtime.
Open an existing saved file and check the project path before editing.
For an execution task, review capability and usage, start it explicitly and follow its job record.
Continue with Saved RTL analysis, Source control or ALcad for a task-specific workflow. Account security settings are described in Account security.
Keep Academy practice work
When an Academy lesson offers a DDS practice link, use it to prepare your own editable exercise project. The verified counter practice opens its saved source and keeps the lesson link nearby. Work in your copy rather than replacing another project.
Confirm the selected organization and practice project, then open the exercise source.
Make the requested change and save the file.
Close and reopen the project, then read the saved source to confirm the change survived.
Before simulation, read the availability message. RTL simulation is currently unavailable in the verified Cloud practice project; opening its simulation page does not produce a waveform or a result.
Reentering the same practice opens the existing project instead of overwriting saved edits. If you need a new attempt, use the explicit new-attempt action when offered and keep the original project. First RTL simulation describes a separate supported native example.
The compact Academy · Practice guide control starts collapsed at the lower-right of the workspace. Open it to read the exercise and use Open code, Open simulation or Back to lesson. Close the guide with its close button, the same control or Esc while the guide has focus.
Return to a project and read Usage
Open a project from Recent projects and confirm its name before editing.
Expand its numbered window row. Use Search windows to find an existing window before opening another.
Read Usage in the navigation panel. Open it for Billing & usage; check the active QUOTA period and reset time before a metered task.
Open a saved file and save a small change. Reopen it to confirm persistence. Open Live Run only to inspect the current run/queue state; it does not itself submit a job.