Windows PC Can Serve Local AI to a Whole Team Without Cloud Access

·2 views

Off Grid AI Desktop, a free Windows app, can turn a single PC with an NVIDIA GPU into a shared local AI server for several people on the same network. Its gateway's Team mode handles multiple requests at once, with the concurrency limit set by GPU memory, and queues extra requests or returns HTTP 429 when full. Users can enable per-person API keys with optional expiry dates and revoke them if a device is lost. Setup involves using the PC's local network address and port 7878, and allowing the app through the firewall only on private networks. Because all requests stay on the local network, code and documents are not sent to a cloud service.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Guide Compares Six Task Management Tools for Air-Gapped Teams

Running a task tool in an isolated network requires more than choosing a self-hosted option, since installation, dependencies, licensing, updates, and required services must all work without internet access. The guide evaluates six options, including ONES.com, Redmine, Taiga, Azure DevOps Server, GitLab Self-Managed, and TaskJuggler, against air-gap readiness, task workflow, collaboration, and project-planning fit. It notes that administrators may need to transfer installation and update packages into the isolated network manually. The authors recommend confirming each product's offline requirements for a specific environment before selecting a tool. Teams are advised to match the tool to the work they actually track, such as issues, schedules, boards, or individual tasks.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Open-source CRM erxes Faces 2024 Auth Bypass and Path Traversal Flaws Fixed in 1.6.2

Security researchers counted roughly 3,394 internet-facing erxes instances, an open-source CRM with a plugin architecture, in an October 2026 scan. SonarSource disclosed three vulnerabilities in June 2025 affecting versions before 1.6.2. The most severe, rated 9.8, let attackers bypass authentication by forging a User HTTP header and reach any GraphQL endpoint. Two other flaws, rated 5.4, allowed unauthenticated file reads and authenticated file writes through path traversal. The findings suggest the problems stem from services trusting a header set by a gateway, so each component must be checked and updated individually, not just the front end.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Guide: Summarizing Moderation Reports with Claude API and Per-Tenant Budgets

The article explains how to use the Claude API in Node.js to create short summaries of moderation reports, with each tenant assigned its own token budget. Summaries serve only as a first-pass aid, while the original report is preserved and any unclear or incomplete output is routed to a human reviewer. The author argues that budgets should be tracked alongside tenant IDs rather than in a global dashboard, and that explaining per-tenant usage matters more than choosing a particular model. The example code routes requests through an OpenAI-compatible endpoint so the provider details stay isolated behind an adapter. It checks estimated input size against the remaining budget, retries rate-limited requests, and returns a review-needed status when budgets are exceeded or responses fail.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Claude Code Scheduled Tasks Silently Stop in Three Ways, Study Finds

A developer running Claude Code's scheduled tasks unattended on a desktop app found the jobs stopped in three distinct ways. Runs were skipped when the machine was asleep or the app closed, though they executed on the next launch. Some runs died mid-execution after a dropped API connection, with no retry mechanism, so the slot was lost. Some slots were also silently switched to disabled without anyone intending it. The author notes none of these failures appear in logs of the affected runs, so they judge success by whether output artifacts reached git rather than whether a run occurred.

0 comments Read more at DEV Community