Getting started
Welcome to Avenlo docs
Avenlo is a cloud notebook platform built for AI-assisted technical work. This guide covers the platform model, runtime workflow, workspace file lifecycle, and billing controls so teams can run reliable production notebook operations.
Welcome to Avenlo
Avenlo combines notebook authoring, runtime orchestration, and usage-aware billing in one product. Instead of treating notebooks as local files only, Avenlo keeps workspace state durable and streams runtime events into the interface.
This approach supports consistent execution feedback, recoverable sessions, and clearer operational boundaries for serious analysis workloads.
Quickstart
- Sign up or log in.
- Create a workspace from the dashboard.
- Start the workspace runtime session.
- Run notebook cells and inspect output streams.
- Upload project files and continue iterating with AI assistance.
Tip: keep one workspace per analysis context to preserve clean runtime state and predictable file scope.
Core concepts
- Workspace: the collaboration and storage boundary for notebook state, files, and access control.
- Runtime session: the durable compute lifecycle that executes code cells and emits event updates.
- Notebook events: streaming updates for cell status, outputs, and notebook mutations.
- Credits: usage accounting across AI and runtime activity with period-based visibility.
Workspaces
Workspaces are the main unit of ownership and collaboration. From dashboard flows, users can create, search, rename, share, and delete workspaces based on role.
Runtime controls are integrated at the workspace level to keep operational actions close to context.
Notebook runtime
Avenlo uses durable runtime sessions. Cell runs, status changes, and outputs are emitted through runtime events and reflected in the notebook UI.
This enables reliable long-running workflows and reduces drift between backend execution state and frontend notebook state.
Files and data
Each workspace includes file upload, download, list, and delete operations. Files remain scoped to the workspace so notebooks and runtime behavior stay deterministic per project.
This model keeps data handling explicit while preserving a simple notebook authoring experience.
Credits and usage
Avenlo uses a bucket-based credit system. Credits are deducted when you use AI features and when notebook runtime activity incurs metered usage. The billing UI shows both your total currently spendable credits and the underlying bucket breakdown.
The three credit buckets
- Free period credits: 3,000 included credits per active billing period.
- Subscription period credits: paid-plan credits for the same billing period. Basic includes 19,000 plan credits and Pro includes 99,000 plan credits.
- Purchased credits: top-up credits bought separately from a paid subscription. These remain on your account until used, but they are only spendable while you have an active paid subscription period.
How billing periods work
Free users receive their 3,000 included credits on a calendar-month basis. The period starts on the first day of the month and resets on the first day of the next month.
Paid users use the subscription period reported by Polar. That same subscription period controls both the 3,000 included free-period credits and the paid-plan credits for that plan.
- Free plan total included credits per month: 3,000.
- Basic plan total included credits per subscription period: 22,000.
- Pro plan total included credits per subscription period: 102,000.
What resets and what rolls over
- Free period credits expire at the end of the current billing period and do not roll over.
- Subscription period credits expire at the end of the current billing period and do not roll over.
- Purchased credits do not expire at period end and remain on your account until used.
If your paid subscription ends, any unused purchased credits stay on your account balance, but they are not spendable again until a new active paid subscription period is in effect.
How credits are deducted
Whenever Avenlo needs to consume credits, it always spends from buckets in the same order:
- Free period credits
- Subscription period credits
- Purchased credits
That means included credits are always used before any top-up credits are touched.
Reservations and final usage
Some actions reserve credits before final usage is known. When that happens, the reservation is allocated against specific buckets using the same spend order described above.
When the work finishes, Avenlo consumes the final amount from those same bucket allocations and releases any unused reserved credits back to the original buckets.
Plan changes and top-ups
Top-ups can only be purchased while you have an active paid subscription. If you are on the free plan, or if your paid subscription period has ended, the product will block top-up checkout.
If you upgrade from one paid plan to another during the same subscription period, Avenlo grants only the difference needed to bring that period up to the target plan's included credit amount. It does not grant a second full plan allocation for the same period.
If you cancel a paid subscription, your subscription remains active until the end of the already-paid period unless otherwise stated at checkout or by law. During that paid-through period, purchased credits remain spendable.
What the billing UI shows
- Available credits: the credits you can spend right now.
- Current period grant: the included credits for the current billing period, which equals free-period credits plus any subscription-period credits.
- Purchased credits on account: the total unused top-up credits still attached to your account, even if some or all of them are temporarily locked because you do not currently have an active paid subscription.
Subscriptions
Subscription management includes plan selection, checkout, billing status, pending plan changes, and credit top-ups. Renewal and cancellation states are explicitly represented.
Paid subscriptions determine whether purchased top-up credits are currently spendable and which billing period controls your included credits.
Reliability model
Avenlo prioritizes durable state transitions and event-driven synchronization between runtime and UI. This improves consistency under long sessions and complex notebook activity.
Support
For product and billing support, contact mathias@avenlo.app.
Legal pages: Terms of Use and Privacy Policy.