Founder
Hydite is developed by Yike Wang, founder of Haokir Inc. Our work brings code-aware agents and product infrastructure closer to the people building software.
We believe an AI development workspace should help you move faster without giving up ownership of your code, architecture, or release decisions.
What Hydite does
Hydite connects a code editor, project-aware agents, model access, and development workflows in one workspace. Ask an agent to explore a repository, plan a feature, edit files, run permitted commands, and report what changed.
The agent supports reusable skills, configured MCP tools, structured questions, and focused subagent sessions. Independent work can run in the background or in a dedicated Git worktree, while permission rules define what requires your approval.
Who Hydite is for
Hydite is for people building complete products, not just generating isolated snippets.
- Founders: turn an idea into a working project and refine it through code and conversation.
- Developers: inspect the repository, review changes, and use agents for implementation, testing, and debugging.
- Agencies and studios: reuse skills and repeatable workflows across client projects.
- AI builders: connect models and MCP tools through a project-aware workflow.
- Product teams: keep requirements, interface decisions, and implementation close together.
One workspace, connected services
Hydite is the development workspace. Studio is the account, organization, project, and billing control plane at dashboard.hydite.com. Zorker provides connected infrastructure services that also apply to Hydite projects.
OpenLink handles project runtime and deployment. Computer provides isolated workspace compute. E3, KV, Zero, Pulse, Flow, Vault, and Insight cover storage, caching, serverless data, messaging, workflows, secrets, and observability. Availability depends on the service, organization entitlement, and current configuration.
A project is a resource-isolation boundary; the organization owns its shared commercial allowances. Included capacity, runtime consumption, and optional paid overages are different concepts — the pricing page makes those boundaries explicit.
What Hydite supports
- Code-aware agents: planning, editing, tool execution, questions, and review within configured permissions.
- Model choice: select configured providers and models for an agent instead of tying every workflow to one model.
- Skills and integrations: load project instructions, supporting files, and external tools through skills and MCP.
- Session continuity: keep the prompt, tool results, reasoning summaries, and changes in the same timeline.
- Parallel work: delegate scoped tasks and use isolated worktrees when needed.
- Version control: inspect changes and preserve a reviewable path from implementation to release.
- Project infrastructure: connect runtime, storage, data services, and deployment through the product control plane.
Clear boundaries for plans and usage
Organization plans define shared platform capacity and credit. Code plans provide user-level coding allowances for Hydite. Token plans provide an optional organization-level API allowance. Project settings configure isolated resources; they are not a second organization subscription.
Computer is a Zorker service available in Hydite. Included Computer slots describe capacity, not unlimited runtime. Additional slots may be purchased on eligible plans, and actual runtime draws from the shared platform credit. Studio remains authoritative for eligibility, availability, and final charges.
Why it matters
Generating code is only one part of shipping software. The work also needs context, execution, testing, access boundaries, and review. Hydite connects those steps so you can understand what the agent did and decide what happens next.
The goal is not to replace developers. It is to let agents handle more repeatable execution while people keep control of product direction, architecture, quality, and release decisions.
What’s next
Our direction is deeper agent coordination, reusable workflow tooling, and a closer connection between development and product operations. Roadmap ideas are not promises of current availability; each feature must be validated in the application and its deployment environment.