Open-weight models, deployed where your data lives.

Llama, Qwen, Mistral, Gemma, and Whisper-class models, plus vision and classic machine learning models, served on hardware or private cloud you control. We have worked with open-weight models since early 2023 and use them in our products today.

Pick the runtime that fits the job.

Serving options, fine-tuning, and speech models. We choose them after testing your workload.

Ollama, llama.cpp, GGUF

Quantized models on CPUs and workstation GPUs. Suited to local assistants, edge boxes, and air-gapped sites.

vLLM and Hugging Face TGI

High-throughput GPU serving with continuous batching and OpenAI-compatible endpoints for team-scale workloads.

LLamaSharp for .NET

In-process inference inside C# services and desktop apps. No Python sidecar and no separate model server to operate.

Azure AI, AWS Bedrock, SageMaker

Open-weight models hosted in your own cloud account when you want managed GPUs with your existing identity and billing.

Fine-tuning and LoRA

Adapters trained with transformers and PEFT on your data, evaluated against your tasks before they reach production.

Speech: wav2vec2 and Whisper

Transcription and audio understanding that stays on your machines, for call recordings, dictation, and archives.

From model card to on-call.

  • Model and license review: which weights fit the task and the legal terms
  • Quantization, GPU sizing on NVIDIA and AMD, and cost modeling before hardware is bought, and the servers themselves if you want us to build them
  • Serving behind a gateway with auth and observability, often WolfPackAI
  • Evaluation on your documents, calls, and workflows, not public benchmarks alone
  • Fine-tuning when prompting runs out
  • Retrieval over your documents with local embeddings (private RAG), and tool-calling models for AI agents
  • Operations: upgrades, rollback, and model version tracking

Why open weights

With a local deployment, model requests stay on your infrastructure. You control the hardware budget and model version. If you choose a hosted model, we document which requests go to that provider.

Not every job suits an open model. We say so in discovery and bring in closed models where that is the better answer.

Small models for structured choices.

Laya is a small open model we run for structured choices: pick from your list, score on your scale, or answer yes or no when a large language model is the wrong tool. It can run on your hardware, with people reviewing consequential decisions.

For example, a model could suggest which team should handle a support ticket. We test its suggestions on your examples and decide with you when a person must review them. A fixed set of answers does not guarantee a correct choice.

A local model for Chat411, too.

Chat411 is part of PalmConnect, an early release. It answers and transfers calls on Asterisk or FreePBX and supports two conversation paths today.

Local path

Chat411 can use a local model on this same stack. Media can be encrypted, and PSTN access is not required. Internal extensions, intercom, on-net SIP, and closed voice networks can keep conversation audio on infrastructure you control without a cloud model provider.

Cloud realtime path

Chat411 can also stream caller audio to a cloud realtime voice provider, xAI by default, when you accept that egress. Call control stays on your PBX. This is a separate choice from the local model path.

View PalmConnect and compare the two voice paths.

Models that see, and the classics that still work.

Plenty of useful models never write a sentence. Some look at images and video. Others are small classifiers trained on your own records, and they are often the fastest and cheapest answer.

Segmentation

Meta's Segment Anything (opens in a new tab) models outline any object in an image or video from a click or a box. They are released under Apache 2.0, run on your own GPUs, and make a good first step for measuring, counting, or redacting what is in the frame.

Pose estimation

Pose models find the joints of a body in each frame, turning video into coordinates your software can check for posture and movement. They run on local GPUs, so the footage stays with you.

Grounded image questions

Apple's Ferret (opens in a new tab) answers questions about a region you point to and marks the objects it names. Apple licenses it for research use only, so it suits evaluation and prototypes; production work moves to a model with commercial terms.

Classic machine learning, since 2010

Edgett has worked with the Accord.NET Framework (opens in a new tab) since its first public release in May 2010, when it brought support vector machines, decision trees, and computer vision to C#. Later work moved to ML.NET, including custom models that predict business behavior, and to page classification and image recognition for claims documents.

A classifier trained on your own records can run on an ordinary CPU and be retrained quickly when the data shifts. When the question is narrow and you have labeled examples, it is often the right tool. Models such as Laya can return a choice or score from text when your application needs a structured answer.

Still running Accord.NET?

The project was archived in November 2020, so it no longer gets fixes. We can keep your models running as they are, or retrain them on a maintained library such as ML.NET and check that the new model agrees with the old one before you switch.

Open weights we already ship.

Two of our products run open-weight embedding models on the user's own device.

Audio Search

Audio Search runs multimodal text and audio embeddings on-device with ONNX Runtime, so text-to-audio and audio-to-audio search work without uploading a file. Available by request.

The same on-device embeddings are the retrieval half of the private RAG systems we build.

Contributions you can check.

Small, merged, and linked. Each one came from running these tools in real work.

HuggingSound, contributor

PR #92 (opens in a new tab) restored installs on Torch 2 and Python 3.11 for a speech toolkit built on Hugging Face Transformers. Merged August 2023.

LLamaSharp, contributor

PR #386 (opens in a new tab) fixed the AVX512 Windows native build for the .NET llama.cpp bindings. Merged December 2023.

Early to open weights, since 2023.

Each entry sits next to the release it followed, so the gap is visible.

  1. — Ran open-weight LLMs on an internal GPU cluster at a healthcare technology company, in the months after Meta released LLaMA (February 2023).
  2. — Opened HuggingSound PR #92 (opens in a new tab), restoring installs on Torch 2 and Python 3.11 ten weeks after PyTorch 2.0.1 shipped (May 8, 2023). Merged August 27.
  3. — Created Blazor Chat (opens in a new tab), a local Llama 2 and Orca 2 chat app on .NET 8, about a week after Microsoft released Orca 2 (November 20) and two weeks after .NET 8 shipped (November 14).
  4. — Fixed the AVX512 Windows build in LLamaSharp (opens in a new tab) when the library was seven months old (created May 9, 2023).
  5. — Shipped Audio Search with on-device multimodal embeddings via ONNX Runtime, within four months of the model's public release (April 1, 2026).

From model selection to a hardened deployment.

  1. Selection pilot

    Shortlist candidate models, review licenses, size the hardware, and stand up a serving path. Evaluate on your data and leave with numbers, not opinions.

  2. Harden and operate

    Gateway, auth, observability, fine-tuning where it pays off, and runbooks for upgrades and rollback so your team owns the deployment.

Run the models on your terms.

Schedule a discovery session. We will map open-weight options to your hardware, data boundaries, and workload.