Components, templates, design and tools for agentic work Private alpha · free for now
Legal

Private Alpha Terms.

The Hub, Terminal and Baselumen are in a private alpha. These terms set out what that means for your access, your work and your bill.

Version
3.0
Effective
Applies to
Every account using the products during the private alpha
Contents
  1. What the private alpha is
  2. Access
  3. What can change
  4. Paying during the alpha
  5. Your work during the alpha
  6. Availability and support
  7. Confidentiality
  8. Feedback
  9. When the alpha ends

The short version

  • Access is by invitation or approval, it is personal, and we can end it.
  • The products are pre-release: features change, move and are removed without the notice a finished product gets.
  • Billing is not switched on yet. When it is, you pay for the products as they stand on the day, not for features on a roadmap.
  • There is no service level, and alpha software can lose data. Keep your own copies.
  • Unreleased features and anything we mark confidential stay confidential.

A summary for convenience, not part of the document. The numbered sections below govern.

What the private alpha is #

The products wearing the Alpha label are real, working software that we use ourselves, and they are still being built. Features ship quickly, interfaces move, and things break before we catch them. The label exists so that is never a surprise.

These terms sit on top of the Terms of Service and the policies it incorporates, which continue to apply. Where these terms conflict with them, these terms win for as long as the products are in alpha.

Access #

  • Access to the private alpha is by invitation or approval. We decide who takes part, and we may limit the number of agencies, workspaces, seats, sites or anything else during it.
  • Access is personal to the account and agency we admit. It may not be sold, transferred or shared.
  • We may pause or end any participant's access to the alpha, or the alpha as a whole, at any time. Where we end the alpha as a whole, we will give notice, and you will be able to export your content.

What can change #

During the alpha we may add, redesign, rename, limit, move between plans or remove any feature, product, limit or integration, without the notice period a finished product gets. Where a change affects something you have built, such as a published site, a saved document or an API key, we work to migrate it rather than break it, and we announce anything we cannot migrate first. That is our intent, not a guarantee.

Billing is not switched on yet, so the products are free today and no plan is charged. We will give notice before billing is switched on, and you will see the price and choose before anything is charged. Nothing converts silently. From the day billing is switched on, the rest of this section applies.

  • You pay for the products as they stand. A plan bought during the alpha buys access to the products as they are on the day, for the period paid. It does not buy any feature on a roadmap, in a preview, in a demo or promised in conversation, and no purchase depends on one.
  • No refunds for alpha changes. Fees are not refunded because a feature changed, moved to another plan, was removed, did not arrive, or did not meet your expectations, or because the alpha ended or moved to general availability during a period you paid for.
  • Alpha pricing can change. Prices, plans and limits offered during the alpha may change at renewal, and any alpha discount or early pricing ends when we say it does. A price change never applies to a period you have already paid for, and is announced before it applies to you.
  • Everything else is the billing policy. Renewal, cancellation, failed payments, chargebacks and taxes work as the Billing, Refunds and Chargebacks policy sets out.

Your work during the alpha #

Alpha applies to the product, not to the ownership of your data. What you make is yours (see the Terms of Service), it is stored with the same care as everything else we run, and we do not plan to reset accounts or wipe content between releases.

Alpha software can lose data. Keep your own copies of anything that matters, and export regularly. To the fullest extent the law allows, we are not liable for content lost, corrupted or made unavailable during the alpha.

Availability and support #

There is no service level, uptime commitment or service credit during the alpha. We aim for the same uptime as any of our production services, and alpha reports go to the people writing the code. Tell us what is broken at support@stacklumen.com.

Confidentiality #

Features, products and plans that we have not released publicly, and anything we mark as confidential or share with you only as an alpha participant, are confidential. Do not publish, share or disclose them, or screenshots, recordings or benchmarks of them, without our written permission. This does not cover anything that is already public, or your own content.

Feedback #

The alpha is when feedback moves the product most, and we read all of it. Anything you send us (bug reports, ideas, complaints, votes) we may build on without obligation or payment to you, as the Terms of Service sets out.

When the alpha ends #

When a product leaves alpha, these terms stop applying to it and the Terms of Service applies on its own. Your account, workspaces and content carry over. Leaving alpha will never mean starting over.

These are the binding terms Stacklumen operates Baselumen by. The short version at the top of each document is a summary and does not change it. Nothing here is legal advice to you; if a decision depends on these terms, ask your own counsel. Earlier versions are available on request, and anything that looks wrong or unclear can be raised at support@stacklumen.com.