Billing policy

This page explains how SoftFission checks balance, charges reserved credits when a compute node becomes ready, returns unused reserved credits after early deletion, separates billed compute activity from free workspace activity, and applies the current storage and startup-credit rules.

Imprint Terms Privacy Compute node

Reservation

Prepaid

Credits for the selected maximum duration are charged only when the compute node becomes ready.

Billing unit

Started hour

Compute-node activity is billed at 1 credit per started hour after the node becomes ready.

Storage

1.00 GB

Persistent project storage is separate from compute activity and remains available between runs.

Provider and scope

This page explains the billing model currently used for SoftFission.

Provider	92 Research ApS
Service	SoftFission
Related pages	This billing policy should be read together with the Terms, Privacy page, and Imprint.
Last updated	2026-03-30

1. Core billing rules

These rules define when balance is checked, when credits are charged, and when unused credits are returned.

When a user starts creating a compute node, the user selects a maximum reserved duration. SoftFission checks that the account balance is sufficient, but no credits are charged yet.

When the compute node is ready, the full reserved amount is charged.

If the user cancels compute-node creation before the node is ready, there is no credits change.

The billing rate is 1 credit per started hour of compute-node activity.

If the compute node is deleted before the reserved duration is fully used, the unused reserved credits are returned to the account credit balance. This return is a credit-balance adjustment, not a cash refund.

The reserved duration may be extended at any time by reserving additional credits.

2. Billed and non-billed activity

Workspace actions are treated differently from compute-node activity.

Compute node activity	Billed at 1 credit per started hour after the node is ready.
Editing files	Not billed as compute activity.
Uploads and downloads	Not billed as compute activity.
Other front-node actions	Free and excluded from compute billing.
Persistent storage	Each user has 1.00 GB for project inputs and results.

3. Compute-node lifecycle

These rules affect the remaining reserved duration and the continuation of billing.

Start

A node can start creation only if the account balance is sufficient for the chosen maximum duration.

Ready state

The full reserved amount is charged when the node is ready, not when the start request is submitted.

Extension

Additional credits may be reserved later to extend the allowed duration.

Early deletion

Unused reserved credits are returned when the node is deleted before the reserved duration is consumed.

Idle state

The compute node is automatically deleted after 1 hour without queued or running compute jobs. A compute node cannot remain active beyond its reserved duration and is deleted when that duration expires.

Workspace

Project files and stored results remain in persistent storage independently of a running compute node.

4. Job submission and walltime

Job acceptance depends on the remaining reserved duration, but runtime is not guaranteed.

A compute job may be submitted only if its selected walltime fits within the remaining reserved duration of the compute node.

SoftFission does not guarantee that a calculation will finish within the selected walltime.

If a job exceeds its selected walltime, it is stopped automatically by the scheduler.

Users should choose walltime conservatively and, when runtime is uncertain, first run a smaller test case before starting a larger production calculation.

5. Interpretation notes

These notes clarify how this page relates to the rest of the product.

Help and billing policy

The Help page provides a practical explanation of compute reservations and credits. This page is the formal policy summary for billing behavior.

Credit value

The monetary value of a credit may change. This page defines credit-based usage rules rather than a fixed fiat price.

Scope

This policy applies to the MVP compute-node workflow and the associated project storage model.

Changes to billing terms

Billing-related parameters may change as the service evolves.

92 Research ApS may update prices, credit packages, included storage, technical limits, or other billing-related parameters in the future.

Unless mandatory law requires otherwise, such changes apply prospectively from their stated effective date and do not retroactively change compute-node activity that has already been charged.