Frequently Asked Questions

Deployment Pricing for Doze in Production

The cost of deploying Doze in production varies depending on your specific configuration needs. We offer flexible deployment options, allowing you to choose your preferred provider, and we will set up your system accordingly. Our pricing is based on a per-node or maintained server unit model, with a monthly fee of $35 per unit.

To illustrate the estimated costs, let's consider an example scenario: serving a large audience of 10,000 simultaneous active users, requiring 10 app server instances, 1 load balancer, and 1 database with 2 backup instances. In this case, the total cost would be approximately 13 units x 35 = 455 per month. Please note that this cost does not include the fees charged by your selected hosting provider for the unit types you choose.

For instance, if your hosting provider offers a general plan at 40 per month, you would need to add 520 to the total cost. Additionally, your hosting provider may charge you for excess bandwidth usage, which would be billed separately. If you opt for custom hosting, a one-time setup fee per unit will apply. We guarantee optimal settings for your units, whether you choose a simple VPS, Dockerized, or Kubernetes setup.

To discuss your custom hosting needs and obtain a quote, please contact us. We will work with you to determine the best solution for your requirements and provide a detailed estimate of the costs involved.

Access to Custom Hosting Provider for Production

Yes, you will have full control and access to your custom hosting provider for production. We require that you add our public key to each unit, which will enable us to access the units and assist with configuration and setup. This access will also allow our staff to manage the system and troubleshoot any issues that may arise.

If you are using containerized systems such as Kubernetes or Dockerized containers, you may need to share your credentials with us to enable our staff to manage the system and perform troubleshooting on your behalf. This will ensure that we can provide you with the necessary support and maintenance to keep your system running smoothly.

Please note that we will only use this access to perform tasks that are necessary to manage and maintain your system, and we will always work in accordance with your instructions and preferences.

The Need for a New Language

DoZe is a transpiled language, which means we build upon existing technologies rather than reinventing the wheel. Our goal is to complement and enhance existing languages, rather than replace them entirely.

That being said, we understand that every project has unique requirements, and sometimes a custom solution is needed. If you have a specific language in mind that you'd like to use with DoZe, we offer the option to create a custom core build tailored to your needs. This requires a license purchase and a development fee, which will enable our team to create a bespoke core for the language of your choice.

By offering this flexibility, we aim to provide developers with the freedom to choose the best tool for their project, while still benefiting from the features and functionality that DoZe provides.

Why We Don't Offer Low-Code or Visual Scripting for DoZe

At DoZe, we prioritize 100% full customization support, empowering developers to have complete control over their projects. We believe that this level of flexibility is essential for creating tailored solutions that meet specific needs.

Unlike some other platforms, we don't force users to conform to our standards or rely on proprietary tools. Instead, we provide a framework that enables developers to create custom solutions easily, without vendor lock-in. Our target languages are all open, and when you purchase a license, you gain access to the generated source code.

We also believe that, in many cases, simple code can be a more efficient and effective way to achieve a goal, rather than relying on low-code or visual scripting tools. By providing a flexible and customizable platform, we allow developers to work in the way that best suits their needs, without introducing unnecessary complexity or overhead.

Our approach is designed to support developers who value flexibility, customization, and control, and who want to create high-quality solutions without being limited by proprietary tools or restrictive platforms.

What if no one adopts DoZe?
Rest assured, the continued development of DoZe will not be hindered by a lack of adoption. As a transpiled project, DoZe will continue to evolve and improve over time, with new features being added as needed. Even if no one chooses to adopt DoZe, the project's codebase can still be maintained and updated by individuals who are interested in doing so. This is because the transpiled code is straightforward and easy to understand, without relying on complex syntax or abstractions. As a result, anyone can pick up where the project left off and continue to develop and maintain DoZe as they see fit.
I'm interested in using DoZe, but since it's in closed beta, where can I find developers to help me with my projects?
As a closed beta project, we're excited to offer a limited number of users the opportunity to experience DoZe firsthand. While we're still refining the platform, we're committed to providing support and assistance to our beta testers. If you're interested in using DoZe and need help with your projects, please don't hesitate to reach out to us. We will ensure that you have access to our team of developers who will work closely with you to address any questions or concerns you may have. To sign up for the closed beta, please contact us directly and we'll be happy to assist you.
What is the purpose of the Sponsorware tag? Do I need to be aware of something?

The Sponsorware tag is a solution we've implemented to ensure the sustainability of our project. By designating certain stakeholders as sponsors, we're creating a framework for them to contribute to the project's maintenance and development. This approach ensures that the project remains viable, even if there's no interest from the broader community. In return, sponsors can expect our team to support their projects, as long as they align with our goals and values.

We've introduced this model to address the issues that have plagued open-source projects in the past. Specifically, we've seen large companies take advantage of open-source projects without contributing back or changing their terms unilaterally. With Sponsorware, we're requiring sponsors to contribute back to the project, even if it's just a small amount. This way, the community can make informed decisions about which companies to support, based on their level of contribution.

Our goal is to promote fairness and transparency in the way projects are maintained and developed. We believe that Sponsorware is a more equitable solution than traditional open-source models, and we're committed to making it work for the benefit of all stakeholders involved.