This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
AIPOCH Open-Science
An open-source AI workbench for scientific research
An open-source, local-first, model-agnostic AI research workbench for reproducible scientific discovery.
Hi Product Hunt! I'm Bobo, an AI researcher and developer at AIPOCH.
We're launching AIPOCH Open-Science, an open-source AI research workbench for Windows, macOS, and Linux. It brings papers, data, AI agents, Python/R execution, and research outputs into one persistent workspace.
We built it to make the whole research process easier to work through—from exploring a question and running an analysis to inspecting the results and sharing the work behind them.
Here's what you can work with:
1. Your choice of models
25 preset provider options, including OpenAI, Anthropic, DeepSeek, and NVIDIA Build. Connect GPT, Claude, Grok, Kimi, GLM, and other supported models, use eligible Claude/Codex subscription logins, or connect compatible local models through gateways such as Ollama and LM Studio. Availability depends on your account, agent backend, and API compatibility.
2. Four agent backends
Choose Claude Code, OpenCode, Codex, or CodeBuddy to power your research workflows.
3. Scientific Skills and data access
23 built-in Skills, with another 525 Skills available to install from the marketplace; 37 built-in scientific connectors covering literature, genomics, chemistry, clinical research, and more; plus 10 installable marketplace Specialists.
4. Execution and inspection
Run Python, R, and shell workflows. Inspect generated figures, tables, reports, and notebooks alongside available execution records, artifact versions, provenance, and optional Reviewer checks.
Then comes the part we're especially excited about: .science packages.
A final figure rarely explains the questions, decisions, and intermediate work that produced it. A .science package can carry selected conversation branches, file versions, Notebook records, and verification evidence to another project or computer.
A colleague can inspect the imported research history, learn from your approach, and create a writable copy to explore further. We see this as useful for collaboration, teaching worked examples, and returning to earlier research.
Imported history stays read-only: opening a package doesn't execute code or restore credentials. Recorded checks describe the sender's verification, not proof that the recipient reran the work.
What research task would you try first? And what would you want inside a .science package when picking up a colleague's work?
I'd love your feedback. Thanks for taking a look!
About AIPOCH Open-Science on Product Hunt
“An open-source AI workbench for scientific research”
AIPOCH Open-Science was submitted on Product Hunt and earned 4 upvotes and 1 comments, placing #86 on the daily leaderboard. An open-source, local-first, model-agnostic AI research workbench for reproducible scientific discovery.
On the analytics side, AIPOCH Open-Science competes within Open Source, GitHub and Science — topics that collectively have 112k followers on Product Hunt. The dashboard above tracks how AIPOCH Open-Science performed against the three products that launched closest to it on the same day.
Who hunted AIPOCH Open-Science?
AIPOCH Open-Science was hunted by Bobo Huang. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of AIPOCH Open-Science including community comment highlights and product details, visit the product overview.
Hi Product Hunt! I'm Bobo, an AI researcher and developer at AIPOCH.
We're launching AIPOCH Open-Science, an open-source AI research workbench for Windows, macOS, and Linux. It brings papers, data, AI agents, Python/R execution, and research outputs into one persistent workspace.
We built it to make the whole research process easier to work through—from exploring a question and running an analysis to inspecting the results and sharing the work behind them.
Here's what you can work with:
1. Your choice of models
25 preset provider options, including OpenAI, Anthropic, DeepSeek, and NVIDIA Build. Connect GPT, Claude, Grok, Kimi, GLM, and other supported models, use eligible Claude/Codex subscription logins, or connect compatible local models through gateways such as Ollama and LM Studio. Availability depends on your account, agent backend, and API compatibility.
2. Four agent backends
Choose Claude Code, OpenCode, Codex, or CodeBuddy to power your research workflows.
3. Scientific Skills and data access
23 built-in Skills, with another 525 Skills available to install from the marketplace; 37 built-in scientific connectors covering literature, genomics, chemistry, clinical research, and more; plus 10 installable marketplace Specialists.
4. Execution and inspection
Run Python, R, and shell workflows. Inspect generated figures, tables, reports, and notebooks alongside available execution records, artifact versions, provenance, and optional Reviewer checks.
Then comes the part we're especially excited about: .science packages.
A final figure rarely explains the questions, decisions, and intermediate work that produced it. A .science package can carry selected conversation branches, file versions, Notebook records, and verification evidence to another project or computer.
A colleague can inspect the imported research history, learn from your approach, and create a writable copy to explore further. We see this as useful for collaboration, teaching worked examples, and returning to earlier research.
Imported history stays read-only: opening a package doesn't execute code or restore credentials. Recorded checks describe the sender's verification, not proof that the recipient reran the work.
What research task would you try first? And what would you want inside a .science package when picking up a colleague's work?
I'd love your feedback. Thanks for taking a look!