The Dregn SaaS platform charges variable credits per hour for resources used, similar to a lot of cloud providers. There are no tiers of service, no types of credits, no seat licenses and no contract renewals. Credits are prepaid, non-refundable and never expire, accumulating until used. Credits are currently only available in discounted pre-order blocks of 10000 to ensure a sufficient beta testing period but will be sold at market release in a more granular subscription, on-demand and balance-triggered reload basis.

Pre-orders get a substantial discount and priority access reservations on the onboarding waiting list for the open beta release. Pre-orders will only be available for a limited time and will end as we move from the closed beta pilot to the open beta stage or as determined by a populated short waitlist, whichever occurs first. Credits will then be available at full release pricing to new customers after the open beta. If pricing at release is not as planned, credits will be supplemented to ensure the same fair effective discount. Early adopter beta stage customers will significantly influence our development roadmap through their interactive feedback directly with the Dregn team, have ongoing exclusive early access to new features, free implementation support, a permanent credits discount and unpublished progress updates as we work towards our full market launch.

A customer's credit usage rate is heavily tied to the underlying resources used by the customer such as cloud compute containers/instances, cloud storage space, GPU resources for AI, 3rd party fees or licenses required for some integrations, support load, etc. A typical enterprise's monthly credits usage is projected to start initially between 1,000 and 2,000 credits then ramp up from there with heavier Dregn usage after an optimal training and onboarding period. Large customer networks with multiple Dregn users, numerous integrations and various AI/tool functions running could consume at least several thousand credits per month, still a relatively tiny slice of an enterprise IT network budget and comparable to other enterprise network tool expenses. Specific breakdowns of credit usage and a checklist for efficient onboarding are expected to be detailed before the open beta release.

Following our planned closed beta pilot with a few invitation-only letter-of-intent customers beginning in the fourth quarter of 2025, we will immediately begin onboarding the queued open beta waitlist customers, tentatively around the first quarter of 2026, in an orderly white-glove process with an assigned network engineer and a project manager to boost the waitlist onboarding process. Once the reservation waitlist priority queue is empty, we will move on to a fair queue of unreserved first-come onboarding with support team tickets. In late beta releases before the anticipated fourth quarter 2026 full market launch of our general release, this will shift to a more automated self-service onboarding process with support available as needed. Should the open beta's release be delayed past 2026, we commit to offering an equivalent value in services from selected partners, safeguarding your purchase's value.

Although anyone can purchase credits, the beta testing stages are intended for direct organizations under agreements with non-trivial supported networks of manageable network devices such as typical enterprise customers. Dregn's SaaS platform early releases are planned for customers primarily in the USA and only in the English language. Individuals purchasing credits for the intentions of resale or personal or contractor or managed service provider usage will likely need to wait until at least the general market release to accommodate their use cases as well as global deployment. Accessing any of our beta platforms will first require online acceptance of a future Beta Test Agreement of terms & conditions, including confidentiality, prohibited reverse-engineering, beta participation terms, organizational requirements, feedback responsibilities, acceptable use and other conditions.

Dregn’s SaaS platform is in early development and will be revealed in phases. Dregn's first couple years were in stealth mode, with only a placeholder website, no real social media, an initial team mission to figure out feasible solutions to a long list of network industry problems and a SaaS technology stack design started for that crusade. Until now, hints were disclosed about what was being developed in the lab and an online presence was started to pursue start-up funding while still keeping a low profile. As Dregn progresses to a customer-worthy proof-of-concept in a closed beta pilot, there will be limited public disclosures such as roadmap teasers while beta-stage customers will receive confidential progress updates until they can use the platform on real networks as it is being developed. When Dregn gets through beta testing and prepares a full market launch, a sign-up website will be published with extensive details about the platform, a public roadmap and good-quality documentation.