Frequently asked questions

No. The editor opens a draft at the workspace root and keeps it in your browser, so you can place nodes and wire a graph before signing up. Save and Run are the two actions that require a signed-in account with a verified email address.

Verification proves that the address on the account belongs to you. Saving a graph and starting a run both require a verified address. If the confirmation email never arrives, check your spam folder and request a new confirmation email for the same address.

The public site and the editor are separate origins: n4g5.dev is the read-only site and app.n4g5.dev is the application. Browser storage is per origin, so the site intentionally has no session. Use an “Open the editor” button to cross over, and the editor will use its own session.

Account settings live in the editor, not on this site. Open the editor and use the account menu in the top bar to reach your profile, password and verification settings.

A graph is one canvas: nodes, connections and container settings. A project is a container for related graphs, its owner, its visibility and its members. You run a graph; you share and collaborate on a project.

The project owner invites users and gives them the editor or viewer role. Editors can change graphs and start runs; viewers can read the project but cannot edit it or run it.

A run is allowed when the person starting it or the project owner holds the entitlement to every store asset the graph uses. This lets a team share a project built on a rented or purchased closed asset without giving every member the source.

Use Preview on a public graph card for a read-only canvas that needs no account. Open in editor lets you inspect and change a local copy; when you save, the editor offers Fork instead of overwriting a graph you do not own. The fork lands in your own project and the original stays untouched.

No. The public site only reads public profiles, projects and graphs. A private project answers as not found here, and its graphs are not listed.

A node is one small Python unit with a manifest. The manifest declares its label, parameters and ports; the class named Node reads its inputs and writes its outputs when the runner executes it.

Exec ports carry control flow: when a node finishes, it fires its exec output and the next node in the chain starts. Data ports carry values such as strings, numbers or dictionaries. A node can receive data without being connected to an exec chain, but it will not run until control reaches it.

A group collapses several nodes into one block with its own input and output ports. It keeps a large graph readable and defines a reusable boundary. A closed group from the store shows the same ports but hides the implementation.

A node’s identity is its source, catalog name and version. The editor stamps the catalog version when you drop a node, and the runner downloads exactly that version. If a pinned version cannot be fetched, the run fails instead of silently using a newer one. A node saved without a version resolves to the newest published version.

Yes. A node reference carries a source URL: ScriptGraph catalog nodes come from the package registry at the pinned version, while a third-party source is cloned. The manifest still defines the ports the editor and the runner use.

Log in, add a product variant to the cart and check out with test coins from your wallet. Checkout is idempotent: retrying the same request does not create a second order. A successful checkout creates an entitlement, and the asset appears in the editor’s Library.

SGC is the wallet currency used by this demo store. You can top up the wallet from your account in the editor; these are test coins, not real money. A purchase records SGC in the order and the wallet, and no external payment is taken.

A rental creates an entitlement with an expiry date — the seeded rental variants run for 30 days. A one-time purchase is perpetual. When a rental expires, the asset can no longer be run, but your other assets and the project structure stay intact.

A closed asset is encrypted at rest with AES-256-GCM. Its payload never reaches the browser: you see the manifest and the interface ports, and the API decrypts the asset in memory only when an entitled run starts. The runner still receives ordinary node code for that run.

Only when the variant includes it. A buyout usually includes the source and unlocks the graph or node; a rental usually does not. The variant features on the product page list what is included before you pay.

Purchases and rentals appear in the Library in the editor. Open the editor, then Library; a closed graph is inserted as a locked group and a closed node appears as a store template in the node palette.

On the server, not in the browser. The API finds or creates a Docker container for the graph and posts the run to the orchestrator inside it. The orchestrator fetches the nodes, starts one asyncio task per node and connects their ports with queues.

Every stdout line and node event is posted back to the API, which re-emits it on the runs Socket.IO namespace. The editor console renders it and highlights the node that is currently running.

The most common cause is a pinned node that could not be fetched. The runner fails the run rather than falling back to another version, so the version recorded in the graph is the version that ran. Check the first error line in the console and the node version.

Check the exec chain. A node that receives data but is not reached by an exec connection never starts. Also check that the graph has a Start node connected to the first working node.

Saving needs a signed-in account with a verified email and a graph you own. If the graph belongs to someone else, use Fork. If you started as a visitor, sign in first; the draft is kept in the browser and can be saved after the login round trip.

The two ports have different types. Every port displays its type in the editor; a dictionary output cannot feed a number input. Insert a conversion node such as Parse JSON or a string conversion from the catalog.

The public site only reads public data, and the API may be unavailable. A private project answers as not found, and an unavailable API renders the page’s empty state instead of failing. Try again, then check the project’s visibility in the editor.

Start with the documentation and the tutorial, then open a working example beside your own graph. Account and purchase questions are handled from the account page in the editor.