2373 applications
Meshlan screenshot thumbnail

Meshlan

Meshlan turns your own Linux server into the control plane for a private virtual LAN that connects remote Windows devices as if they sat on the same router. Devices pair through your server, receive their certificates, and then talk directly to each other over encrypted tunnels whenever NAT allows, using dual-stack hole punching, UPnP, and STUN diagnostics to find a path. When a direct connection is impossible, traffic falls back to relays, and multiple relay nodes are chosen automatically by latency, jitter, packet loss, and health. You can publish a service that only listens on localhost, a local API, a web panel, a database, a game server, to the mesh on a custom port, with direct access or manual approval by its creator. Names stay stable while addresses change: devices answer to names like alice.mesh and services to api.alice.mesh, and an HTTPS gateway serves mesh websites without port numbers. Files move directly between devices over the encrypted link while the server only distributes metadata. The console shows the live topology with P2P and relay paths, latency, and service health, and local history keeps traffic and events for replay with a time slider. Optional AI automation keeps model keys on the server, encrypts context end to end, and asks for your confirmation before changing anything. Signed updates verify and roll back automatically when a health check fails. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Immich Insights screenshot thumbnail

Immich Insights

Immich Insights turns the photo library you already keep in Immich into a year-in-review style dashboard of how you actually shoot. Connect it with your own Immich API key and it reads your asset metadata into a local snapshot, without copying your original photos, then builds the overview Immich itself never shows: total photos and videos, storage used, favorites, albums, and your newest additions. Pick any year or a custom date range and see that period's shooting volume, favorites, albums, and devices. Camera statistics break your library down by device and manufacturer, with leaderboards you can correct when the same camera appears under different names. Exposure analysis shows your ISO, focal length, and shutter speed distributions, the focal lengths you reach for most, and how your settings shift by hour of day. Rhythm charts map your shooting by month, weekday, and hour, with a calendar heatmap of your most active days. A zoomable timeline marks the moments that matter: first photo, a new device joining the library, your longest gap, your busiest day ever. People and location views count faces and mapped places by country and continent, and a photography profile scores your habits. Clicking any chart value opens the matching photo thumbnails, and reports export as PDF, CSV, or JPG. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Lalabase screenshot thumbnail

Lalabase

Lalabase is project management built for developers who work with clients, putting tickets, time tracking, documentation, and meetings in one workspace instead of five separate tools. Each client gets an organisation with its own projects and its own access, and roles decide exactly what clients can see. Tasks run as a list or a board with the statuses, priorities, and fields you define per project, rather than the workflow a vendor chose for you. Time tracking records several sessions per ticket, each billable on its own, with exports that go straight into the invoice. Documentation lives beside the work: notes and documents sit in the project, and a folder in your GitHub or GitLab repository becomes the project's docs automatically. Meetings keep their transcript, an AI summary, and the tasks that follow from what was actually said. When you need an answer, the AI assistant takes one question across tickets, comments, documents, hours, and meetings, and it cites the ticket, page, or conversation every answer came from. It even reads your repository's indexed code structurally, so questions about what is implemented get answered against the code. The assistant stays off until you enable it with your own provider key or a model in your own network. An MCP server and REST API let your own agents list, create, and update tickets, comment, and log time. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
Thesys screenshot thumbnail

Thesys

Thesys is a research workspace where you search academic papers, build your own library, and ask questions that answer with citations you can click straight onto the highlighted passage of the PDF. Discovery searches OpenAlex and arXiv in one pool, so a paper you find can be previewed and added to your library without leaving the workspace. Uploaded PDFs are ingested locally, and when you ask a question the answer cites its sources in the document, jumping the preview to the retrieved passage with either a full-passage or a tighter focused highlight. Reader mode opens a paper full-width so you can select any span of text and ask about that exact passage. Document summaries follow a consistent structure of problem statement, methodology, key findings, limitations, and metrics, with citations that still land on the source text. Figures and flowcharts are described during ingest, so questions and summaries can reference them too. When two papers disagree, Compare mode takes one claim and classifies each retrieved pair as corroboratory, contradictory, or neutral, with confidence shown in a side panel. Your bibliography exports as BibTeX, RIS, EndNote, or CSV for whatever reference manager you already use. Papers, embeddings, and chat history stay on your own disk the whole time. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
Dopbase screenshot thumbnail

Dopbase

Dopbase keeps your application secrets out of scattered .env files and stores them, encrypted one by one, in a single self-hosted server you run as one file. You organize everything by project and environment, so the payment service has its own development, staging, and production values, and the same key can hold a different encrypted value in each place. Every secret is an individual record that can be updated, revealed, versioned, or rolled back without touching the others, and reading metadata never exposes a value. When an application starts, one command asks the server for an environment and injects exactly those values into the process, removing its own token before the child process runs. People sign in to the Admin UI with roles for root, admins, members, and even AI agents that can read metadata but change nothing. CI jobs and servers use runner tokens scoped to a single environment, so a staging credential can never read production. You can import and export .env files, edit secrets as a table or as raw env text, connect single sign-on through providers like Keycloak, and read an audit history of checks, reveals, and changes. Full-instance backups and the master key stay under your control on your own disk. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Oh My CPA screenshot thumbnail

Oh My CPA

Oh My CPA gives a CLIProxyAPI gateway a proper control room, where providers, OAuth credentials, client keys, model routing, and the cost of every request are managed and watched from one self-hosted console. You add providers such as Codex, Claude, Gemini, xAI, DeepSeek, Vertex AI, and OpenAI-compatible services, each with credentials, retry and error policies, priority, weight, and an enable switch the gateway actually enforces. OAuth accounts are signed in from the console, with quota window readings, refresh schedules, and per-credential model aliases kept next to the keys they belong to. Client keys can be created, named, and revoked, and those names follow the traffic into request records and filters so you always know which key spent what. The dashboard follows request volume, token throughput, cache hit rate, and cost from the last fifteen minutes out to ninety days, with a year-long token heatmap for the long view. Insights compare keys, models, providers, and credentials against the previous period, while the live routing view shows which credential each request travelled to and whether it was rerouted. Every request stays searchable, with duration, time to first token, token breakdown, and the raw log in a detail drawer. A playground tests any routed model with text and images before your users do. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
FreeSBC screenshot thumbnail

FreeSBC

FreeSBC sits at the edge of your phone system so your FreeSWITCH or Asterisk never has to face the public internet. It is the only element with a public address: phones register through it over SIP on UDP, TCP, or TLS, browsers call through WebSocket with WebRTC terminated at the edge (ICE-Lite, DTLS-SRTP, and RTCP-mux, relayed onward as plain RTP), and carriers reach your switch through it as an outbound proxy, with the switch's private addresses hidden from every SDP body, Contact, and Request-URI it constructs. The switch stays on a private LAN as the registrar and call brain, holding credentials and carrier accounts, while FreeSBC anchors all media on its own ports with hardened first-packet latching and a silence watchdog, and never transcodes. Against the background radiation of SIP scanning, it applies per-IP rate limits with separate limits for carrier sources, scanner fingerprinting with in-memory bans, and admission control for public INVITEs and REGISTER enumeration, and every denial is a silent drop. A multi-switch pool hashes users across switches, and one fixed private socket keeps the trusted side simple. The embedded WebUI, REST API, and Prometheus metrics sit behind a bcrypt-checked admin login, showing live calls and media ports. One static binary, one YAML file, no database, no Redis, and no separate media process to babysit. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Limelit Open screenshot thumbnail

Limelit Open

When a buyer asks ChatGPT, Claude, or Perplexity which product to choose, Limelit Open shows whether your brand appears in the answer, where it ranks, and which sources the engines trusted. You define the prompts your market actually asks, register your competitors, and the tracker runs every prompt against seven engines on a schedule you control: ChatGPT, Claude, Perplexity, and Gemini through vendor APIs with web search on, plus Google AI Overviews, Google AI Mode, and Bing Copilot through scraper providers, each result labeled by how it was collected. Every stored answer is searched for your brand and each competitor with the rank of the list item they appear in, so visibility, share of voice, average position, and citation share rest on readable evidence rather than a black-box score. Click any number and you land on the full answer text with matches highlighted, the searches the engine ran, the brands it named, and every cited URL classified as yours, a competitor's, social, informational, or other. A prompt by engine grid makes weak spots obvious, and the built-in MCP server lets Claude or another assistant query the same data in plain language. Runs are capped by a daily ceiling you set, prompts and answers live in one SQLite file, and a single export command dumps the whole instance as JSON or CSVs for your own reporting. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Ruvio screenshot thumbnail

Ruvio

Ruvio is a Redis-compatible in-memory database that folds the cache, the lock service, the rate limiter, and the delay queue into one Rust process your existing clients already speak to. Connect with redis-cli or the first-party clients for Rust, .NET, Go, Java, Python, and Node.js, and the familiar strings, hashes, lists, sets, sorted sets, and streams are there, 287 commands in all. The difference shows in the primitives that usually need a second system: LEASE grants a fencing token for a key, SEMAPHORE caps concurrent holders with per-holder TTLs, INCRBY with MAX builds a counter that refuses to pass capacity, SETV writes only when your version is still current, CHANGES arms a feed of later writes on a shard, and XADD DELAY stores a stream entry now and reveals it to consumer groups when the delay passes. Each shard owns its keys outright, parsing, recording, and applying without a lock on the hot path, and features cost memory only on keys that use them. Durability is a startup choice you name, memory, snapshot, everysec, or always, written through a write-ahead log, and replicas copy shard by shard while optional coordinators agree through Raft to promote a replica when a primary stops answering. A browser operator UI shows data, command forms, Pub/Sub, and ACL users on the running server. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
RankMe screenshot thumbnail

RankMe

RankMe puts the whole SEO workbench on your own server: audits, rankings, keywords, backlinks, and AI visibility without a per-seat subscription deciding what you may check. Crawl a site and it runs 26 automated checks, returning a plain-language report sorted into Fix now, Watch, and Passed, where each finding names the page, explains in one sentence why it matters, and tells you how to fix it, with an optional AI summary on top. Rank tracking follows Google organic positions over time plus Bing, YouTube, and Amazon, watches SERP features, fires confirmed-drop alerts, and maps local rankings on a geogrid. Keyword research covers volume, difficulty, trends, and SERP-overlap clustering, while Search Console data feeds cannibalization reports and connects to GA4, PageSpeed Insights, and CrUX for performance context. Backlink profiles, link-gap analysis, toxic-link review, and competitor discovery show who links to rivals and which content earns it. A dedicated AI visibility module tracks prompts in AI Overviews and LLM answers and measures share of voice in a weekly digest. Agencies get PDF and CSV exports, scheduled white-label client reports, read-only share links, a REST API, and an MCP server, with alerts delivered by email, Slack, or signed webhook across seven interface languages. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
OpenAgentCore screenshot thumbnail

OpenAgentCore

OpenAgentCore puts Codex, Claude Code, and MiniMax Code behind one self-hosted Agents API, so your applications start agent sessions through the official OpenAI SDK while the work runs on machines you control. Set OPENAI_BASE_URL to your installation and issue a Project API key, and the same client code that talks to OpenAI now talks to your Core. Each session runs a native harness, exactly as it runs on a developer's machine, with the model provider, model ID, and protocol you configure per harness or per session. Choose where sessions execute: microsandbox nodes you operate, Docker, E2B, or a self-hosted workstation, VM, or container connected by the oac-daemon with a credential scoped to one environment. Idle microsandbox sessions release their compute and resume on a compatible node with workspace files intact, so long investigations do not rent a machine while they sleep. The Web console walks operators through setup, tracks sessions and turns, manages models and credentials, and issues keys, while the separate Core API serves operators and the Agents API serves applications. Durable execution state in PostgreSQL keeps events, results, and schedules recoverable across restarts. Sandbox providers, workspace filesystems, harnesses, and model providers all plug in through defined protocols, so every layer can be replaced on its own. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Mistgate screenshot thumbnail

Mistgate

Running a VPN for family, friends, or a small team usually means babysitting servers one SSH session at a time, and Mistgate replaces that with one panel that keeps the whole fleet configured. Add a server from the browser by typing its address and root password: the panel pins the host key, checks the host, opens the ports, and installs the signed node agent for you. Each person gets one subscription link that their app turns into the server list, or a personal AmneziaVPN key per device, so a lost phone can be revoked without touching anyone else. Groups decide which protocol profiles a person receives, while per-user traffic quotas, expiry dates, device limits, and per-device speed limits keep sharing fair. Hysteria2 brings QUIC-based speed with port hopping, obfuscation, and certificate options; VLESS REALITY and AmneziaWG 2.0 and 3.1 cover networks where one protocol gets blocked, and Cloudflare WARP can serve as the exit for all three. Every five minutes the panel connects to each server the way a real client app would, a doctor on every node runs host checks with safe fixes, and alerts reach you on Telegram before your users notice. The public address shows strangers a decoy site while the admin hides behind a secret path, and encrypted backups go to your Cloudflare R2 bucket on a schedule. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
Campfire Rust screenshot thumbnail

Campfire Rust

Your team chat can be one executable on your own server: Campfire Rust runs rooms, direct messages, attachments, and search as a single binary that replaces the whole Ruby, Puma, Redis, Resque, and Thruster stack. Create rooms with access controls for projects, departments, or a private board discussion, and keep direct messages beside them for quick questions. File attachments arrive with previews, mentions pull the right person into a thread, and search finds the decision someone made months ago. Web Push notifications reach browsers and phones, so a quiet room still finds its people when it matters. Chatbots connect through a simple HTTP API for sending and receiving messages and attachments, which makes Campfire a home for build alerts, deploy notices, and support pings. Existing Campfire installs upgrade in place because the Rust binary reads the same SQLite database, storage layout, and signed cookies, with no data migration and no mass sign-out. Automatic TLS with Let's Encrypt certificates, HTTP/2, and Action Cable-compatible WebSockets are built in, and the whole system works on air-gapped networks that never touch the internet. Run it as your primary chat, as a backup for the day a hosted service goes down, or as a walled garden for executives and events. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Litpage screenshot thumbnail

Litpage

A project brief and the task board tracking it belong together, and Litpage keeps pages, databases, and team discussion in one self-hosted workspace instead of scattering them across subscriptions. Write in a block editor with 41 block types, a slash menu, markdown shortcuts, drag and drop, mentions, equations, and highlighted code blocks. The same data becomes a table, board, list, gallery, calendar, timeline, chart, dashboard, feed, form, or map, with typed fields, formulas, relations, and rollups underneath. Automations and buttons turn those databases into working tools, while templates keep repeated projects consistent. Teammates edit together live, comment, suggest edits, and revisit version history, with page-level and field-level permissions deciding who sees what. Pages can be shared publicly or published as sites, and Markdown, CSV, HTML, Word, and PDF files import into the tree. Optional AI runs on the provider and key you configure: chat that searches your workspace, custom agents on schedules or triggers, writing help, database autofill, and meeting-note summaries. Administrators get member and guest management, security policies, an audit log, analytics, passkeys, and two-step verification. A REST API with personal tokens, webhooks, and an MCP endpoint open everything to your other tools. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
OpenTodo screenshot thumbnail

OpenTodo

Plan the day in the morning, capture tasks in your own words as they appear, and let every device settle on the same list by evening: that rhythm is what OpenTodo is built around. The Today view opens with a briefing, a daily limit, and morning, afternoon, and evening sections, with time blocking and meetings counted against the day's real capacity. Quick add understands natural language in six languages, a pasted list becomes tasks in one step, and the command bar, inbox processing, email-to-task, and dictation keep capture fast. Projects organize work with sections, boards whose cards carry notes, timelines, sub-projects, and areas, while recurring tasks and sequential projects handle routines and ordered work. Lists can be shared with the people you live and work with, invited by link once the owner account exists. Every device keeps a full copy and works offline; changes are stamped per field and merge cleanly through your server when you reconnect, with history and undo preserving earlier values. CalDAV and calendar feeds connect your calendars, GitHub and GitLab issues flow in, and webhooks plus ntfy, Pushover, and Gotify send notifications out. Scheduled backups go to a folder, S3-compatible storage, or WebDAV, and the whole server is one container around one SQLite file. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
Ollaya screenshot thumbnail

Ollaya

Ollaya serves decision models that answer typed questions about a message, ticket, or document with calibrated probabilities, through a self-hosted API shaped like the hosted service it can replace. Send a state, which can be an email, a support ticket, or any JSON, plus typed choice, score, and yes or no questions, and the model answers in one forward pass in milliseconds without generating text. Pull models by name the way Ollama users already know, with run, list, ps, show, copy, and remove commands managing the local store. Downloads verify every layer against its sha256 digest, resume when interrupted, and share blobs between models so storage stays lean. Existing TypeSafe code keeps working by changing one environment variable, because the /v1/systemone and /v1/decisions endpoints are wire-identical and the official SDK sends its key the same way. The native /api adds routing information and timings, model loading and unloading, and streamed pull progress for your own tooling. Put it to work triaging inboxes, routing requests to the right model or team, screening prompts for injection and jailbreak attempts, or replacing per-token LLM classification calls with a local answer. Agents reach the same engine through the bundled MCP server, and LiteLLM, LangChain, DSPy, LlamaIndex, n8n, and Dify connect through their existing integrations. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Univer Workspace screenshot thumbnail

Univer Workspace

A budget model, the launch document that explains it, and the slides that present it can live side by side in one self-hosted office workspace that people and AI agents edit together. Personal and Team Spaces organize Sheets, Docs, Slides, relational Bases, and Boards, with Recent, Trash, file import, and export views keeping everyday housekeeping close at hand. Sharing follows role and node aware access control, including anonymous viewing, so a single table or document can be opened to a reader without exposing the whole space. Data and references stay connected across artifacts as the workspace changes, which keeps a figure corrected in a sheet consistent with the document that quotes it. The Workspace Agent drafts and revises content in isolated Worktrees, verifies its own changes, and hands the result to a person for review before anything reaches the trunk. Several review rounds can happen while humans keep editing in the Browser, and nothing merges until someone approves it. The Workspace CLI connects existing agents to your deployment, so automation can create content, inspect data, render screenshots and PDFs, and run layout checks before review. Sign-in accepts passwords, GitHub, Discord, or application OAuth, and files move in and out as XLSX, DOCX, PPTX, and CSV without a separate conversion project. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Cited screenshot thumbnail

Cited

Buyers now ask an AI assistant before they ever visit your website, and Cited tells you whether your brand made it into the answer. Verify your domain with a DNS record, choose the buyer-like prompts worth watching, and Cited checks them on schedule across ChatGPT, Claude, Gemini, Perplexity, Google AI Mode, and Google AI Overviews. Every meaningful appearance becomes a durable evidence note in your citation inbox: open one to see the exact prompt, the response snapshot, where your domain appeared, and the first-seen history. It distinguishes a true source citation from a brand mention without a link, an explicit recommendation, and the uncomfortable one, a missed opportunity where a competitor got cited and you did not. Competitor tracking runs continuously, so you see rivals earning answers in your category while there is still time to respond. Notes can be annotated, organized through new, seen, saved, and resolved states, and exported for reporting. Email alerts flag meaningful new events and a weekly digest summarizes what changed, so checking becomes a habit instead of another dashboard to babysit. Workspace roles and local credentials keep a small marketing team organized on your own PostgreSQL database. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy