Frequently Asked Questions.

Everything you need to know about VibeHard capabilities and availability.

Which editions are currently available?

Only the Community Edition is available today. Agentic Workflows and all other paid tiers are currently on hold / apply for early access. We are rolling out our premium services to select partners in phases to ensure the highest quality of reliability engineering.

What happens if I try to upgrade to Agentic Workflows now?

You will be placed on our priority waitlist. We are actively reviewing applications for the Agentic Workflows tier. Once approved, our team will contact you to begin the onboarding process for your custom SRE service.

Is VibeHard Cloud available for the Community Edition?

VibeHard Cloud gate offload is currently in closed testing. Once released, the Builder Tier ($25/mo) will be available as an add-on for Community Edition users to offload compute-intensive agent tasks.

Do I need VibeHard Cloud to use the agent?

No. The core VibeHard agent (Community Edition) executes entirely locally on your machine via the MCP protocol. Cloud offload is strictly optional for performance scaling.

How do the 43 security gates actually run?

The gates execute in an isolated ephemeral VM that performs rigorous static analysis, AST validation, dependency auditing, and runtime sandboxing checks. Each build artifact is subject to strict deterministic checks, ensuring there are no hidden regressions, memory leaks, or unapproved network egress rules before deployment.

What happens to my workflows if I cancel?

Because VibeHard Runtime executes structurally siloed code within a zero-knowledge architecture, you always retain ownership of the final built software. If you cancel, the active automated remediation and monitoring (BotHard) halt, but your deployed software continues to function indefinitely as standalone binaries.

Can BotHard patch proprietary dependencies without internet access?

Yes. BotHard operates entirely on local context and AST manipulation. It parses standard output, compiler errors, and local package documentation to synthesize patches. No source code or proprietary IP is ever transmitted to a central server for evaluation.