Normal Usage
Most legitimate trial workspaces should not need to think about fair-use controls.
The trial is built for real-project evaluation; fair-use limits keep the service reliable while giving legitimate evaluations room to work.
“Fair Use is about resource consumption - not feature gating.”
Your trial is designed to let you evaluate the SliceFlo product experience, including the project-health workflows that make the product useful.
No credit card required. No automatic charge. Fair-use limits apply.
Most teams evaluating SliceFlo should be able to work normally without thinking about fair-use limits. Controls primarily apply to resource-intensive activity.
Workspace storage and individual file-upload limits help prevent disproportionate storage and bandwidth consumption.
Automations are available during the trial. If the allowance is reached, executions may pause until capacity increases or a paid option applies.
API activity, imports, exports, and similar high-volume operations may be rate-limited or throttled to maintain service reliability.
Large team sizes, project volumes, work-item volumes, migrations, or technical evaluation requirements may trigger a capacity review rather than an automatic workspace block.
SliceFlo applies fair-use controls to the resource involved wherever practical, rather than disabling the entire evaluation.
Most legitimate trial workspaces should not need to think about fair-use controls.
Where practical, SliceFlo provides visibility before a metered resource is exhausted.
Only the affected resource pauses (e.g., file uploads, new automation may stop). The rest of your workspace functions normally.
A fair-use limit on one resource does not automatically make the entire SliceFlo workspace read-only.
Some legitimate evaluations are larger than the standard trial profile. If your organization needs additional capacity to evaluate SliceFlo with real work, tell us what you need.
A broader team needs access during the evaluation.
You need to bring more project or work-item data into SliceFlo.
Your technical evaluation requires additional API throughput.
Real workflows require more automation execution during the trial.
Fair Use helps SliceFlo accommodate genuine evaluation needs. Separate protections exist for activity that threatens platform security, reliability, other customers, or the integrity of the trial program.
Hitting storage limits due to importing extensive team documentation.
Running high volumes of automations while stress-testing workflows.
Inviting a large number of colleagues for a coordinated review session.
Result: Resource pause. Workspace intact. Option to request more capacity.
Using workspaces purely as a free file-hosting or CDN service.
Creating automated accounts in bulk to circumvent trial limitations.
Utilizing APIs for crypto mining, spam distribution, or illegal activities.
Result: Immediate workspace suspension and account review.
No. Fair-use controls are intended to manage resource consumption rather than create hidden feature gates.
Your trial includes SliceFlo's standard product experience, subject to the applicable resource limits.
Normally, no.
Where practical, SliceFlo restricts or throttles only the affected resource.
For example, reaching a storage allowance may pause new uploads without preventing normal project-health work.
Where the resource is metered and advance notice is practical, SliceFlo may notify workspace administrators as usage approaches the available allowance.
Yes.
If additional capacity is genuinely required to evaluate SliceFlo, your organization can submit a capacity request for review.
Not automatically.
Additional trial capacity can be approved for legitimate evaluation requirements without turning the request itself into a purchase commitment.
Large legitimate evaluations may be reviewed so SliceFlo can determine the appropriate capacity and support required.
The objective is to enable genuine evaluation rather than automatically reject larger organizations.
Customer-relevant resource limits can be published where appropriate.
Security, fraud, spam, trial-abuse, and other protective thresholds remain confidential because publishing them could weaken the controls themselves.
Use SliceFlo free for 4 weeks and test project-health visibility across real product and engineering work.