Multi-model operations
Bring hosted APIs, local endpoints, and Puter into one model pool. Run a single model, compare many side by side, or route work dynamically without rebuilding the dataset.
Preparing BatchHive Studio…
The application modules are loading. This usually takes a moment on first visit.
Some application modules failed to load. Features may be degraded — reload the page when your connection allows.
dataflow_* storage keys and DataFlow* runtime namespaces are retained only for backwards compatibility with existing project data.BatchHive AI Studio · V12.31.12
BatchHive combines two focused AI surfaces in one browser runtime: Studio for high-volume, row-aligned batch processing over Excel and CSV datasets, and Chat for interactive multimodal work. Both share the same provider catalog, model pool, and theme system without forcing batch execution and conversation into the same interface.
Platform
Studio and Chat use the same provider catalog, model pool, network layer, search integrations, key storage, and theme system. Their interfaces stay separate so batch operations and conversational work can evolve without competing for the same screen.
Bring hosted APIs, local endpoints, and Puter into one model pool. Run a single model, compare many side by side, or route work dynamically without rebuilding the dataset.
Work directly from spreadsheet rows instead of copy/paste prompts. Variable mapping, row identity, large-dataset storage, and incremental results stay attached to the source data.
Admission happens before a row is claimed. Routing reacts to RPM, TPM, Retry-After, provider cooldowns, daily limits, and available capacity across the selected lanes.
Outputs remain associated with their source rows and execution context. Provenance, route attempts, failure diagnostics, and resumable checkpoints make long runs inspectable.
Product areas
Studio is optimized for deterministic, row-based operations. Chat is optimized for conversation, multimodal context, search, and iterative reasoning. Moving between them never requires a reload.
Configure providers, load spreadsheet data, map variables, define the prompt once, tune execution controls, run at scale with Smart Route or Compare mode, and inspect row-aligned results with provenance, checkpoints, and exports.
Work interactively with the shared model pool: persistent and temporary conversations, branches and message versions, multimodal attachments, reasoning and context controls, manually selected web search, global memory, and Markdown/JSON import & export.
Studio workflow
Jump directly to any stage inside Studio. Provider configuration, dataset mapping, prompt controls, routing state, and results remain connected without turning the interface into one oversized form.
Providers & integrations
Bring your own API keys, sign in to Puter for free hosted access, or point BatchHive at your local endpoints. Smart Route and Compare mode treat every selected lane as one capacity pool, and provider calls go straight from your browser to the provider.
localhost:11434.localhost:1234.Scale & reliability
Large datasets introduce memory, quota, retry, and traceability problems. BatchHive treats those as execution concerns instead of leaving them to the prompt.
Large Dataset mode parses and stores source rows in IndexedDB, executes bounded windows, persists incremental results, and keeps checkpoints resumable. The active window stays small even when the source file is not.
Capacity checks happen before work is assigned to an execution lane.
Transient failures can release rows to another eligible provider or model.
Transport IDs and persisted ordinals keep outputs bound to the intended source row.
Security & data handling
BatchHive has no application backend: provider, dataset, chat, and search traffic runs from your browser directly to the services you configure. Datasets, results, checkpoints, and conversations are stored in your browser's storage — including disk-backed IndexedDB for large datasets — not on a BatchHive server.
Provider keys are convenience storage, not a secrets vault: saved keys are obfuscated in local or session storage, never presented as encrypted, and can be cleared in one action. Restricted keys and trusted devices remain the right operating practice. When the app is hosted on Puter, network requests may fall back to Puter's networking relay, and that behavior stays visible in transport diagnostics.
Requests go from your browser to the configured provider; there is no BatchHive middleman server that sees your prompts or data.
Session-only by default, optional persistence, XOR obfuscation in storage, and a one-click "forget everything" control.
Results export to Excel/CSV, conversations export to Markdown/JSON, and large runs stream their output incrementally.
Route attempts, retry budgets, cooldowns, quota scopes, and provenance stay visible in the Run and Results workspaces.
Choose your surface
Both surfaces share the same BatchHive foundation, so you can move between structured execution and conversation without rebuilding provider or model configuration.
Access 500+ AI models (GPT-5, Claude, Gemini, DeepSeek, Llama…) for free.
Sign in once with your free Puter account — no API keys needed ever.
Upload and inspect the source file, then move on. This remains a focused setup step—not the main workspace.
| Upload a dataset to preview rows. |
Upload a dataset and map variables to preview the final per-row prompt.
Token budget and optional batch protection.
| Run a job to preview results. |