Networks, critical to everything, still waste time & money, increase risks & frustration and stress people & processes. Dregn's AI-native integration & automation, intuitive game-like 3D visibility & control and future-of-work roadmap are a long overdue networking industry revolution.
Spread the word, back the cause, join the list!
Tell the world about Dregn
There are many ways to support Dregn's mission. The easiest is to follow us and share Dregn with your connections and followers.Pre-Order Dregn SaaS Credits
For a limited time, secure early adopter access with a prioritized waitlist reservation and exclusive discount by pre-ordering blocks of 10K Credits now at an additional 40% off already-halved beta pricing.
Dregn SaaS Credits FAQ:
What are Dregn Credits?
Dregn Credits are the proprietary internal currency which the Dregn SaaS platform charges at variable rates per hour for resources consumed, similar to a lot of cloud and AI providers. There are no tiers of service, no plan upgrades, no types of Credits, no seat licenses and no contract renewals. Credits are prepaid, non-refundable , never expire and accumulate until used. Credits are currently only available in discounted pre-order blocks of 10000, sufficient to ensure onboarding and beta usage. After beta stages, Credits will be sold at full pricing in more granular subscription, on-demand, balance-triggered reload and other options.
Why pre-order Dregn Credits?
Pre-orders get a substantial discount, 70% off the anticipated $1/Credit full price at market release, and prioritized access reservations on the onboarding waitlist for the open beta release. Pre-orders will only be available for a limited time, ending with the move from the closed beta pilot to the open beta stage or as determined by a well-populated waitlist, whichever occurs first. Credits are anticipated to be available at half price through the open beta period. If pricing at market release is not as planned, pre-ordered Credits will be supplemented to ensure the same fair effective discount. Early adopter beta stage customers will significantly influence the 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 through the beta and market release launches.
How are Dregn Credits used?
A customer's Credit usage rate is heavily tied to the underlying resources consumed by the customer such as with cloud compute containers/instances, cloud storage space, AI GPU resources, 3rd party fees or licenses required for some integrations, support load, etc. Typical enterprise monthly Credits usage is projected to start initially between 1000 and 2000 Credits then ramp up to heavier Dregn usage after an optimal training and onboarding period. Large customer networks with thousands of devices, multiple Dregn users, numerous integrations and various AI/tool functions running could consume at least several thousand Credits per month, still a relatively thin slice of a large organization's IT network budget and comparable to other enterprise network tool expenses at scale. Specific breakdowns of Credit usage and a checklist for Credits-efficient onboarding are expected to be detailed before the open beta release.
When can Dregn Credits be used?
Following a planned closed beta pilot with a few invitation-only letter-of-intent customers beginning around the end of 2025, Dregn will begin the onboarding of queued open beta waitlist customers, anticipated in the second half of 2026, in an orderly white-glove process with an assigned network engineer and a project manager to boost the onboarding process, so pre-order customers can begin using their purchased Credits. Once the reservation waitlist priority queue is empty, Dregn will move on to a fair queue of unreserved first-come early adopter customers onboarded with support team tickets. In late beta releases before the tentative 2027 full market launch of Dregn's general release, this will shift to a more automated self-service onboarding process with support available as needed. Should the open beta's release or pre-order onboarding progress be delayed past 2026, Dregn commits to offering an equivalent value in services from selected Dregn partners to any customer wishing to exit the waitlist, safeguarding the pre-order purchase value.
Who can use Dregn Credits?
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 deployments. 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.
Where is this Dregn platform?
Dregn’s SaaS platform is in early development, is not yet available to use 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, only hints were disclosed about what was being developed and an online presence was started to pursue start-up funding while still keeping a low profile. As Dregn progresses through customer-worthy beta releases, anticipated from 2025 to 2027, there will be limited public disclosures such as roadmap teasers while beta-stage customers will receive confidential progress updates about the platform as it is being developed. When Dregn gets through beta releases and prepares a full market launch, a sign-up page will be published with links to extensive details about the platform, a public roadmap and good-quality documentation.
Buyer agrees to and acknowledges the risks of pre-ordering services for an unreleased platform still in early development with no set release date. Credits are prepaid, non-refundable , never expire and accumulate until used. A future beta test agreement of terms & conditions will require online acceptance to use the platform at the time of release. It is very important to provide accurate reliable contact information. Read FAQ.
Sponsor-a-Feature
Sponsor prioritized development time toward a feature and help build Dregn faster.
Sponsoring FAQ:
What is Sponsor-a-Feature?
Sponsoring development of individual features provides a way to influence the direction and functionality of Dregn by prioritizing features and proving market demand with sponsors sharing the cost of creating a feature. Sponsorships also allow more developers working in parallel in different roadmap lanes and feature branches for accelerating the overall platform. Contributing toward a large feature, enhancement of an existing feature or a few small related features grouped into one work effort benefits the Dregn user community as a whole and steers efforts beyond platform architecture.
Why sponsor a feature?
Perhaps there is a need for Dregn to do, handle or integrate something. It could be something not thought of, a cool idea not yet requested, a niche use case or an idea buried in a backlog of hundreds of unsponsored roadmap features not in the top 100. A sponsorship reranks the idea high on the list. Sponsoring a feature is different from a general project donation or purchase of Credits, both also welcome, and prioritizes a feature to ensure a certain allocation of work toward its implementation. Sponsors will also receive unpublished updates and priority support.
How will a sponsorship be used?
The bulk of prepaid sponsorship funds, from a single sponsor or co-sponsor group, will be applied directly to associated developer costs in rough increments. A small slice will cover costs of related resources to implement the feature including compute, devops, testing, project management, vendor interop, hiring experts and other resources at the discretion of Dregn with no profit taken from sponsorships. Sponsorship may often not pay for the full feature work effort, which cannot be estimated and may be divided into parts, but will prioritize it, ranked by sponsorship totals, in active work load.
When will sponsored features be ready?
First, a detailed feature request must be worked out between the sponsor and Dregn then aligned to be future-safe compatible with roadmap features and architectures. If it strays too far from the platform vision or does not blend well with the roadmap, a best effort will be made to implement it in a form that makes sense with modifications at Dregn's discretion. The time to implement even a fully sponsored feature from request to availability will vary, potentially weeks to months and subject to change, with the work required and complexity. The sponsor may test and give feedback when the feature is ready.
Who can sponsor a feature?
A sponsor or co-sponsor in a group must be a contactable user or organization, not a competitor or conflict of interest, and have a serious, reasonable, not troublesome or counterproductive, feature request. While a sponsor may not be a user or on the onboarding waitlist, it is preferred that a sponsor use and test the feature. A sponsor is only a feature requestor as all feature developments, sponsored or not, are the property of Dregn, which retains all ownership, control and exclusive rights. A pseudonym may optionally be mentioned and thanked as a feature sponsor in an agreed way or left anonymous by default.
Where will a feature be presented?
Experimental features are confidentially released to sponsors and testers until sufficiently tested and refined to be announced for all Dregn users and maintained as part of the Dregn platform. Features may not appear exactly as requested or may be tied to other features as they may share prerequisite critical-path dependencies that require prioritized work efforts to resolve as they hold up multiple features. There may be optimizations to defragment roadmap features by combining the best ideas and work efforts from multiple similar features to implement a single more robust feature.
Sponsor agrees to and acknowledges the risks of sponsoring a feature for an unreleased platform still in early development with no set release date. Dregn retains all ownership, control and exclusive rights. A pseudonym may optionally be mentioned and thanked as a feature sponsor in an agreed way or left anonymous by default. It is very important to provide accurate reliable contact information. Read FAQ.