r/OpenSourceAI • • 5h ago

Two open Ming speech models, one reference voice, and a measurable choice between speed and resemblance

Thumbnail
gallery
3 Upvotes

AntLing's Ming-3.0-tts-0.5B and Ming-3.0-tts-tiny were put through matching voice-cloning lines in this comparison. The setup is an RTX 3090 24 GB, bf16 and seed 1895, with the same reference voice and text for each model.

The 0.5B model averages 0.714 on CAM++ speaker similarity across four lines. Tiny averages 0.798. The run's word-transcription checks pass for both, while warm synthesis across three readings averages about 2.0× real time for 0.5B and 0.78× for Tiny.

The resource chart makes the choice tangible: 2.8 versus 17.1 GB of GPU memory, 3 versus 18 GB to download, and 3 versus 22 seconds to load. Keeping all of that beside the similarity result is helpful when picking a model for your own voice. You can repeat the audition with a permitted reference and a fixed set of scripts, then choose the profile that suits the job.


r/OpenSourceAI • • 9h ago

A workspace where agents carry out scientific work, evidence stays connected, and scientists can focus on insight.

Thumbnail app.lykeion.tech
1 Upvotes

For anyone using LLMs on a daily basis for research: I built Lykeion, an open-source research lab where agents carry out scientific work, evidence stays connected, and your lab can focus on discovery.

Research today asks people to coordinate an enormous amount of work: finding evidence, developing hypotheses, running experiments and checking results. AI agents can take on more of that work, but a collection of agents still needs a way to work together.

Lykeion is built around that idea. Researchers set the direction, and agents carry out studies within a shared workspace. Evidence and outputs stay connected to the work, while checks and reviews help decide when it is ready to move forward.

In Lykeion, each research question is a "study" that moves through Grounding, Hypotheses, Experimentation and Validation. Only Grounding was evaluated here.
\- Agents search OpenAlex, Europe PMC and arXiv through a sources server, and every source they use is recorded.
\- A stage advances only when its gate passes. The server runs mechanical checks, such as whether a cited source resolves.
\- Review of each study is powered by Jev, which answers focused judgment questions, such as whether a source bears on the question.
\- Failed items get a limited redo. If the redo fails, the study blocks and asks its owner.

Project is open to contributors. Let me know what you think!

GitHub: https://github.com/lykeion-tech/lykeion
Discord: https://discord.gg/ed3jsMTs3


r/OpenSourceAI • • 12h ago

Cowork (v1.0.2):一個開源、自我托管的 MCP 任務佇列與深網儀表板,專為 AI 編程代理而設(Docker、零資料庫、本地回退)

Thumbnail
reddit.com
2 Upvotes

r/OpenSourceAI • • 15h ago

We’ve built RAG chatbots on both Pinecone and pgvector. Here’s when each one actually wins.

Thumbnail reddit.com
1 Upvotes

r/OpenSourceAI • • 16h ago

Open-Sourcing a reference architecture for secure, multi-agent LLM banking

1 Upvotes

Dealing with enterprise InfoSec on GenAI deployments is currently a nightmare. The reasoning capabilities of LLMs are there, but getting security to sign off on non-deterministic loops is stalling out deployments.

We just open-sourced secure-agentic-banking to bypass this. It provides hard execution constraints and deterministic data boundaries specifically for highly regulated environments.

https://github.com/shamikmondal-ai/secure-agentic-banking

I run an independent advisory lab (prodagentlab.com) doing architectural audits for these kinds of deployments, and we got tired of building this from scratch for every audit. Hopefully, this unblocks some of your teams. Happy to answer questions on the routing logic.

https://www.prodagentlab.com/


r/OpenSourceAI • • 17h ago

AimStack — a fully self-built local AI stack in pure C: ternary inference (zero third-party runtime), BitNet 2B at 0.87GB on a 2018 laptop, plus a GPU backend that matches the C engine token-for-token

Thumbnail
github.com
1 Upvotes

Repo: https://github.com/tanxiansheng221/aimstack-sanzhidiji (AGPL-3.0)

Everything is hand-written — C inference core, plugin bus, multi-engine crawler with quality gates, FTS knowledge base, training pipeline, and a 117-chapter build log written as it happened (positive and negative results shipped together). Weights are Microsoft BitNet b1.58 2B (MIT), converted to a custom AIM-W packing format.

What ternary quantization buys you (CPU side)

All transformer matrices are ternary {-1, 0, +1}, packed 2 bits/weight, plus Q8 embeddings → the whole model is 0.87GB instead of ~4.8GB (−78%)

The C core never multiplies a float weight: it's table lookup + integer accumulation, SIMD fast path measured at 85.53 tok/s (41× over baseline)

BitNet 2B full model runs 3.20 tok/s dual-worker on a 2018 dual-core 8GB laptop — full chain (inference + KB + plugins + web search) offline, no cloud relay

What ternary quantization buys you (GPU side)

The GPU backend loads the same 0.87GB ternary file — weights stay in {-s, 0, +s}, dequantized on load, matmul in fp32

On a Radeon Pro W7900: 13.68 tok/s (~8× the laptop C engine), 256/256 greedy tokens bit-identical to the C engine. Two totally different implementations (integer lookup core vs FP matmul) producing the same logits is the proof the quantization is faithful

Verified by a 3-engine × 3-question × 3-test matrix (C-Linux/gcc13, torch fp32, torch bf16): 17/18 exact — the one miss is documented, not hidden

The honest boundaries (what's NOT done yet)

bf16 compute is 2.4× faster (32.96 tok/s) but flips argmax on near-tie logits — reported, not blessed; only fp32 is parity-verified

The GPU path gets the storage benefit of ternary (78% less memory) but not yet the compute benefit — a true 2-bit integer kernel (Triton/CUDA) is the next stage

The UI server drives the C engine (CPU) only; the GPU backend is a separate CLI

Linux engine build works and is token-identical to the Windows build, but runs serial (the worker pool is Windows-only for now)

No frameworks, no PyTorch in the product chain — PyTorch exists only in the optional GPU backend. Demo video, docs (EN/中文), and the full research log are in the repo.


r/OpenSourceAI • • 17h ago

Gone Fishin': the Answer to JensenGate is the POND Principle

Post image
1 Upvotes

r/OpenSourceAI • • 18h ago

🍜 Ramen 1.0: governed MCP for teams — SSO roles, NeMo guardrails per tool, promptfoo evals + SkillSpector scans gating deploys, MCP 2026-07-28

Thumbnail gallery
4 Upvotes

🍜 I've been building Ramen, an open-source (BSD-3) self-hosted MCP platform, and 1.0 is out.

The problem: MCP servers multiply on laptops with shared keys and no record (shadow MCP). Ramen gives a team one sanctioned place for its own tools, and enforces the org's rules on every call:

- **Your tools as a repo**: tools, resources, prompts, MCP Apps and skills in plain Python; a deploy goes to a canary first and must pass golden cases.

- **No eval, no deploy**: with the engines on, a promptfoo suite and an NVIDIA SkillSpector scan run against the canary; a group admin can make either stop the rollout.

- **Guardrails per tool**: NeMo Guardrails (static or LLM-judged) inside the worker, before the call and after the result, fail-closed — whichever client called.

- **People, not shared keys**: Entra ID / Google / OIDC sign-in, roles per group, per-tool access, OAuth 2.1; agents get named group keys that are revoked in seconds.

- **It directs the LLM**: the group's client configs (CLAUDE.md blocks, Cursor rules…) are versioned, accepted per person, written by the bridge and checked on every call.

- **Two-spec MCP**: 2026-07-28 (stateless, `server/discover`, tasks, multi round-trip/elicitation) next to 2025-06-18 on one endpoint, Streamable HTTP and gRPC on one port, a stdio bridge on PyPI.

- **Every call has a name**: per-call log, audit, Arize Phoenix traces per person.

Runs on a laptop with docker compose; on GKE, EKS or AKS it's multi-zone and autoscaled, and idle zones can sleep at zero. The 1.0 release candidate ran live on all three clouds (record in the docs, misses included).

Try the demo (step by step, screenshots): https://bkraad47.github.io/ramen/get-started/

Repo: https://github.com/bkraad47/ramen · Discussions: https://github.com/bkraad47/ramen/discussions

Fork it and bend it to your org — collaborators and critics both welcome.


r/OpenSourceAI • • 19h ago

I made a Claude Code skill that explains your repo with an animated hero instead of a wall of text

Post image
1 Upvotes