BharatCode Minion 1
BharatCode currently runs on BharatCode Minion 1. Live stats shows the real queue, serving capacity, hardware load, model route, and throughput from that shared resource.
Why BharatCode exists
BharatCode exists because the tools that shape professional software work should not depend on who can pay for them. One plan at ₹699 a month, unlimited within fair use — and free for students with a valid .ac.in or .edu.in email, because they need it the most.
BharatCode does not pretend GPUs are unlimited. The price stays low because the serving pool is shared openly: usage, queue depth, and capacity stay visible so the community can use the resource with care.
BharatCode currently runs on BharatCode Minion 1. Live stats shows the real queue, serving capacity, hardware load, model route, and throughput from that shared resource.
Pro subscriptions cover serving, web, auth, domain, monitoring, and platform storage — so free student access never depends on charity holding out.
Live stats exists so users can see the shared resource plainly. If the server is busy, the product should say so.
The path is simple: keep the current server useful, learn from real usage, then add capacity in visible milestones. Focused usage helps more students share the same compute pool.
The first milestone is sustained daily usage on BharatCode Minion 1, with enough utilization to justify the next capacity purchase.
The next stage is purpose-built Indian infrastructure using carefully selected older GPUs where the unit economics can support free student access.
Queue depth, utilization, tokens, and serving capacity stay visible so the community can understand the resource it is sharing.
BharatCode is built toward Indian data residency and local infrastructure. Models can change as better open-weight releases appear; the strategic commitment is that serving and product data move toward an India-first operating model as we scale.
Unlimited use is a promise about pricing, not physics — the resource is finite. Off-peak usage, thoughtful prompts, and visible stewardship scores keep the cluster useful without turning the product into an API-key quota maze.