Feature Requests & Pricing.

Who This Is For

VoxelSite is for:

• Business owners who want a website without learning a page builder
• Freelancers who build client sites and want to move faster
• Developers who want a self-hosted AI tool they can extend and customize

Whether you're a bakery that needs a simple website or a developer churning out client projects, VoxelSite works for you. See use cases for detailed scenarios.

Your data stays on your server. Your generated websites are standard files you own forever.

Please review the demo carefully before purchasing.

Buy What Exists

When you purchase VoxelSite, you're buying the product as it exists today. The feature set on the demo site is exactly what you get.

We release updates regularly, and those updates are free for the lifetime of the product. But the mindset that leads to satisfaction: expect nothing beyond what you see today. If the current feature set solves your problem, buy it. If it doesn't, don't buy it hoping we'll add what you need.

Every update we ship is a bonus, not a promise fulfilled.

The Math Behind the Product

Before requesting features, understand the economics.

VoxelSite costs $29. After payment processing fees and taxes, we receive roughly $18–20 per sale.

Now consider what a single feature request actually costs to build properly:

That's 180 to 660 sales just to break even on a single feature — before accounting for the support tickets it generates.

When someone says "just add X," they're asking us to invest weeks of development funded by hundreds of future sales, while we continue to fix bugs, answer support tickets, and maintain everything that already exists.

We consider every suggestion. But we weigh it against the reality of running a product at this price point. Every hour on a new feature is an hour not spent fixing bugs, improving stability, or helping existing customers.

We are not refusing features because we don't care. We are making hard choices because the economics demand it. Every feature has an opportunity cost. At $8–9 net per sale, that cost is real.

Why Feature Requests Don't Drive Our Roadmap

We read every suggestion we receive. Some are genuinely good ideas. But we don't build features on demand.

Nothing Is "Simple"

We regularly hear "just add X, it's simple" or "this should take five minutes." With respect: no, it doesn't.

A feature that sounds like "just add a button" involves:

• Designing how it fits within the existing architecture
• UI changes across the Studio interface
• Updating AI prompts and generation logic
• Documentation updates
• Testing across different hosting environments and AI providers
• Edge cases that only surface after release
• Supporting it forever — across every hosting provider, PHP version, and AI model

What looks like a toggle on a settings page might touch dozens of files and require weeks of careful implementation.

If you're a developer, you already know this. If you're not, please trust that the people who built this product understand what's involved better than someone looking at it from the outside.

Features Have Dependencies

Building software is sequential. Feature X often requires Features A, B, and C first. The visible feature is the tip of an iceberg.

We build features top-down. The first iteration ships with core functionality, then gets refined over subsequent releases. What you see now is the current state, not the final state. But "later" might mean six months or longer depending on priorities.

No Published Roadmap

Publishing a roadmap creates expectations we can't reliably meet. When priorities shift because reality demanded it, we'd spend more time explaining why the roadmap changed than actually building software.

We know the general direction. We don't pretend to know every step of the journey.

We Have a Vision

VoxelSite is designed to be a clean, reliable AI content website builder that does core mechanics extremely well. We're not building a full-featured CMS, an e-commerce platform, or a marketing automation suite.

When someone suggests a feature that doesn't fit this vision, the answer is no — not because it's a bad idea, but because it's not the right idea for this product. We'd rather do fewer things well than many things poorly.

Complexity Is the Enemy

Every feature we add has a cost:

• More surface area for bugs. Each new feature interacts with every existing feature. The number of possible interactions grows exponentially.
• More to learn. A simple product is easy to understand and recommend. A complex product requires tutorials, videos, and a learning curve that keeps people from getting started.
• More to support. Every feature generates questions, edge cases, and hosting-specific issues.
• More to maintain. Code doesn't maintain itself. Features that exist today need to keep working through every future update.

We've seen what happens when products try to be everything: they become bloated, unreliable, and impossible to support at script pricing. We choose the opposite path.

What We Will Not Do

To be unambiguous:

• We will not add features because someone demands them. Politely or otherwise.
• We will not rush features to satisfy a deadline you haven't told us about. If you need something by next week, hire a developer.
• We will not add third-party integrations on request. Integrations create permanent maintenance obligations with services we don't control. When that service changes their API, we inherit the support burden.
• We will not build features that make the product harder to use for everyone else. A feature that helps 2% of users but confuses the other 98% is a net negative.
• We will not compete on feature count. We compete on quality, reliability, and the fact that you own your output.

None of this means we don't listen. It means we evaluate every request against the reality of building a sustainable product at this price point.

We Are Not Google

Some feature requests implicitly compare VoxelSite to products built by companies with hundreds of engineers and billions in revenue.

We cannot and do not pretend to match the feature output of venture-funded companies with 200-person engineering teams. What we offer instead:

• You pay once, not forever
• You own your files
• Your data stays on your server
• No lock-in, no proprietary formats
• The product works without an internet connection (except for AI generation)

If you need the feature velocity and support response time of a well-funded hosted platform, that product exists — and it costs $20–50/month. There's no shame in choosing it. But you can't expect enterprise-level support and updates at one-time-purchase pricing. That math doesn't work for anyone. Use this product as a starting point and customize it to your needs.

Our Priorities

Our development time is limited. We are very deliberate about how we spend it. These are our priorities, in strict order:

1. Bugs and stability. This is non-negotiable and always comes first. If something is broken, we fix it. Every customer deserves a product that works reliably. This is where the majority of our development time goes — and it should be.

2. Security issues. Anything that could compromise data or system integrity.

3. Support. Helping customers with real problems. This takes significant time and always takes priority over new development.

4. AI generation quality. Making the generated websites better, more varied, and more aligned with what you describe. This is the core value proposition — it has to be excellent.

5. Stability improvements. Making existing features work better across more hosting environments and AI providers.

6. Quality of life improvements. Small refinements that make daily use smoother.

7. New features. We build these when items 1–6 are in good shape. Not before.

Notice where new features sit on this list. Last. Not because we don't want to build them, but because shipping a new feature while existing features are broken would be irresponsible. A product that does 10 things unreliably is worse than a product that does 5 things well.

A lot of development work is invisible — you don't see "fixed edge case where AI generation failed with specific Tailwind configuration on PHP 8.3 with Nginx" in a changelog and think "great update." But that's what keeps the product reliable. That's what makes it trustworthy enough to use for real client projects.

Pricing

VoxelSite costs $29 for a Regular license. This is a one-time payment with lifetime updates included.

Already at the Floor

After payment processing and taxes, we retain roughly 60-70% of each sale. At current volumes, revenue does not yet fully cover ongoing development and support costs. This is an investment in a product we believe in.

We don't offer individual discounts. The price reflects the value and the cost.

Compare to Alternatives

Hosted AI website builders charge $15–$50+ per month. VoxelSite costs less than one month of most alternatives, and you own it forever.

With hosted platforms, your website lives on their infrastructure. They change pricing, get acquired, or shut down — your website goes with them. VoxelSite generates framework-independent PHP files. Delete _studio/ from your server and the published site keeps running.

"But AI Costs Money Too"

Yes. VoxelSite uses external AI providers, and you pay for API usage directly. But AI costs for website generation are typically very low — a few cents per page. Compare that to $20+/month for a hosted builder, and VoxelSite pays for itself almost immediately.

You Have the Source Code

Every license includes complete, unencrypted source code. If you need a feature we don't provide:

• Build it yourself if you're a developer
• Hire a developer to build it
• Commission a freelancer to extend the platform

The codebase is PHP with a clean architecture. Any competent PHP developer can work with it.

Custom Work

We are available for custom development work. However, this is priced at agency rates — not script-support rates.

Building a production-ready feature involves design, implementation, testing, documentation, and ongoing maintenance. A "simple" feature request often represents $2,000–$10,000+ of development work.

If you need something custom, contact us to discuss scope and pricing. Just understand this is separate from the license purchase and priced accordingly.

Providing Useful Feedback

For bugs:

• What happened?
• What did you expect?
• Steps to reproduce
• Your environment: PHP version, AI provider, hosting provider
• Error messages or screenshots

For suggestions:

• The problem you're trying to solve, not just the feature you want
• How you're currently working around it
• Whether you've checked the demo and docs first

We read everything. We respond to bugs. We rarely respond to feature requests beyond acknowledgment — there's usually nothing actionable to say.

Setting Expectations

You're purchasing a powerful development tool for roughly the cost of a cup of coffee. The price reflects our bet on volume.

We're a small operation. Support responses can take four or more working days. If your business depends on same-day responses, you need a managed platform with enterprise pricing and enterprise support. That's not us.

Your bug reports make the product better for everyone. Your feature requests are read but rarely implemented. Understanding this makes for a better experience on both sides.

A Note on Tone

We occasionally receive aggressive messages demanding features, threatening bad reviews, or comparing VoxelSite unfavorably to products with 100x our resources. We understand frustration, but we want to be clear:

• Demanding a feature does not make it appear faster. It makes us less likely to engage.
• Threatening a bad review to pressure development is not feedback. It's coercion, and it doesn't work.
• Comparing our output to Google Sites, Wix, or Squarespace while paying $29 instead of $240/year is not a reasonable comparison. You're welcome to use those products — they're excellent for what they charge.

We respect customers who report bugs, describe problems thoughtfully, and understand the tradeoffs of independent software. Those relationships make this work sustainable.

Summary

• Buy the product for what it is today, not what it might become
• Feature requests are read but rarely implemented
• Bugs and support always come first — new features come last
• We cannot match the output of venture-funded companies with hundreds of engineers
• Pricing is already at the minimum sustainable level
• You have full source code to extend as needed
• Complexity is the enemy — we add features carefully, not quickly

We'd rather have customers who understand these tradeoffs than customers who expect something we can't deliver.

For more on why product teams say no to good ideas, see Intercom's Product strategy means saying no.