- Free open source alternatives of paid software.
Paid software
Free open source alternative app list about topic "self-hosted" :
CertD
CertD is a self-hosted certificate control panel that automatically requests free certificates from ACME providers like Let's Encrypt, installs them into Nginx, and reloads or restarts Nginx afterward.
Free
Windows
macOS
Linux
Certimate
Certimate is a self-hosted SSL certificate management console that automatically applies for, renews, and deploys free certificates from ACME CAs like Let's Encrypt to Nginx or other targets, all from a friendly Vue 3 web interface.
Free
Windows
macOS
Linux
novel-plus
novel-plus is an open-source web-novel (original fiction) publishing CMS built with Java, Spring Boot and Vue. It combines a reader-facing novel site, an author writing studio with AI-assisted writing, an admin console, and crawler/import tooling, with Docker deployment support.
Free
Windows
macOS
Linux
ModStart
ModStart is an open-source, Laravel-based modular rapid development framework for building CMS, blog, portal and admin sites, featuring a one-click module marketplace, RBAC permissions, membership/API modules and developer scaffolding. ModStartBlog is the blogging application built on top of it.
Free
Windows
macOS
Linux
memos
✨ Featured sponsor: CodeRabbit — Industry-leading AI code reviews . Memos Your thoughts, your data, shared on your terms. Memos is a timeline for your notes, and it belongs to you. Write in Markdown, post in seconds, and choose who sees each memo: just you, the people you invite, or anyone with the link. Run with Docker · Try the live demo · Read the docs Why Memos? Write first — Save a thought without choosing a title or folder. Memos are written in Markdown and can include images and files. Find it later — Search, filter by tag, or look back through any day on the timeline. Pin what matters and save the filters you reuse as views. Yours to keep — Self-host Memos with zero telemetry , MIT-licensed source , and a full export of your memos. Share when you choose — New memos are private. Make one visible to signed-in users or public when you want to share it. Explore all features → Quick Start Run Memos with Docker: docker run -d \ --name memos \ -p 5230:5230 \ -v ~ /.memos:/var/opt/memos \ neosmemo/memos:stable Other install options are in the deployment guide . Releases use YY.MM , with optional point releases such as 26.09.1 and release candidates such as 26.09-rc.1 . Calendar release tags have no v prefix. The Docker stable tag follows stable releases; canary follows development builds. If upgrading from a release before v0.31.0, run v0.31.0 successfully. See the upgrade requirements for earlier versions. Web Clipper Save pages, selections, and images from your browser straight into Memos as source-linked Markdown. Get the Memos Web Clipper for Chrome or Firefox . Sponsors Love Memos? Sponsor the project on GitHub . Get Help Read the docs , join Discord , or ask in GitHub Discussions . Found a bug or have an idea? Open an issue . To contribute, see the contributing guide . Star History
Free
Windows
macOS
Linux
Android
iOS
Open WebUI
Key features Self-hosted AI chat interface that you can run on your own hardware, keeping conversations and data under your control. Works with both local models (for example via Ollama) and remote LLM providers from a single web UI. Extensible, community-driven project designed to be customized and adapted to different workflows. Multi-model support, letting you switch between different language models without leaving the app. Browser-based chat experience that requires no client installation beyond a modern web browser. Platforms: Windows, macOS, Linux. Links Official website Source code Pricing: Fully free and open source under the MIT license; self-hostable Docker image with no paid tier.
Free
Windows
macOS
Linux
Khoj
Key features Search across personal notes, documents, and the web from a single chat interface Automates tasks and acts as a personal research assistant Self-hosted design that keeps your data on your own infrastructure Functions as an AI "second brain" for organizing and retrieving knowledge Open-source codebase licensed under AGPL-3.0 Platforms: Windows, macOS, Linux Links Official website Source code Pricing: Freemium. A free, self-hostable open-source release under AGPL-3.0 is available, and a hosted cloud version with usage limits is also offered.
Freemium
Windows
macOS
Linux
LocalAI
Key features Self-hosted AI runtime covering text, voice, vision, and agent capabilities. OpenAI-compatible API, making it a practical free alternative to the OpenAI API. Runs LLMs and other AI models locally, keeping data on your own hardware and off external services. Works across Windows, macOS, Linux, and Raspberry Pi OS. Fully open source under the MIT license — no usage limits or API fees. Platforms: Windows, macOS, Linux, Raspberry Pi OS Links Official website: https://localai.io Source code: https://github.com/mudler/LocalAI Pricing Free. Completely free and open source under the MIT license; self-host all AI features without usage limits or API fees.
Free
Windows
macOS
Linux
Raspberry Pi OS
ByteChef
Key features Low-code platform purpose-built for creating AI agents and automating complex, multi-step workflows. Hundreds of pre-built integrations make it easy to connect your favorite tools and services. Self-hosted design means you retain full control over your data, deployment, and infrastructure. Runs on Windows, macOS, and Linux for flexible installation options. Licensed under Apache-2.0 with no limits on the number of workflows or users. Platforms Windows, macOS, and Linux. Links Official website: bytechef.io Source code: github.com/bytechefhq/bytechef Pricing Free. ByteChef is completely self-hostable and free under the Apache-2.0 open-source license, with no limits on workflows or users.
Free
Windows
macOS
Linux
LobeChat
Key features Open-source, modern AI chat interface for managing, building, and running AI agent teams. Works across multiple LLM providers, letting you switch or combine models in one place. Supports self-hosting for full control over your data and deployment. Extensible via plugins to add custom tools and capabilities. Rich feature set covering chat organization, agent management, and team workflows. Platforms: Windows, macOS, Linux Links Official website: https://lobehub.com/ Source code: https://github.com/lobehub/lobe-chat Pricing Free and fully open-source under Apache-2.0. You can self-host it or use the public demo.
Free
Windows
macOS
Linux
LibreChat
Key features Unifies multiple AI models — including OpenAI, Anthropic, and others — into a single conversation platform. Supports plugins to extend functionality. Enables sharing conversations and configurations. Self-hosted deployment for full control over your data and setup. Platforms: Windows, macOS, Linux Links Official website Source code repository Pricing Free. Fully free and open-source under the MIT license; self-host your own instance with no usage limits.
Free
Windows
macOS
Linux
Hexabot
Key features Self-hosted platform for building AI agents, chatbots, and automation workflows — a free, open-source alternative to ManyChat. Deploy your chatbots across multiple messaging channels from a single interface. Design automation workflows to handle complex, multi-step user interactions. Maintain full control over your data and infrastructure thanks to self-hosting. Completely free to use with no feature limitations under the GPL-3.0 license. Platforms: Linux Links Official website: https://hexabot.ai Source code: https://github.com/hexabot-ai/hexabot Pricing: Free. Completely free and open-source under the GPL-3.0 license; self-host without limitations.
Free
Linux
puter
puter is a free, open-source alternative to Dropbox . The Open-Source Internet Computer! « LIVE DEMO » Puter.com · App Store · Developers · Discord · Reddit · X Puter Puter is an advanced, open-source, self-hostable internet computer designed to be feature-rich, fast, and highly extensible. For Users Puter's goal is to provide you with every app and feature you need to work, create, and play under one roof. From a simple Notepad and Voice Recorder to Spreadsheet and Camera , Puter wants to be the all-in-one solution for your digital life. For Developers Puter provides everything you need to build and publish web apps and games. From AI to Cloud Storage and Database to Serverless Workers , Puter has you covered. Puter also helps you get users! Once you build your app, you can publish it on our App Store to reach and monetize users. Getting Started 💻 Local Development git clone https://github.com/HeyPuter/puter cd puter npm install npm start → This should launch Puter at http://puter.localhost:4100 🚀 Self-Hosting Linux/macOS curl -fsSL https://puter.com/selfhost | sh Windows irm https: // puter.com / selfhost?os = windows | iex → For more details, see Self-Hosting Puter . ☁️ Puter.com Puter is available as a hosted service at puter.com . Support Connect with the maintainers and community through these channels: Bug report or feature request? Please open an issue . Discord: discord.com/invite/PQcx7Teh8u X (Twitter): x.com/HeyPuter Reddit: reddit.com/r/puter/ Mastodon: mastodon.social/@puter Security issues or abuse reports?
[email protected]
Email maintainers at
[email protected]
We are always happy to help you with any questions you may have. Don't hesitate to ask! License This repository, including all its contents, sub-projects, modules, and components, is licensed under AGPL-3.0 unless explicitly stated otherwise. Third-party libraries included in this repository may be subject to their own licenses. Translations Arabic / العربية Armenian / Հայերեն Bengali / বাংলা Chinese / 中文 Danish / Dansk English Farsi / فارسی Finnish / Suomi French / Français German / Deutsch Hebrew/ עברית Hindi / हिंदी Hungarian / Magyar Indonesian / Bahasa Indonesia Italian / Italiano Japanese / 日本語 Korean / 한국어 Malay / Bahasa Malaysia Malayalam / മലയാളം Polish / Polski Portuguese / Português Punjabi / ਪੰਜਾਬੀ Romanian / Română Russian / Русский Spanish / Español Swedish / Svenska Tamil / தமிழ் Telugu / తెలుగు Thai / ไทย Turkish / Türkçe Ukrainian / Українська Urdu / اردو Vietnamese / Tiếng Việt
Free
Windows
macOS
Linux
OpenMontage
OpenMontage is a free, open-source alternative to Runway . Monty the Clapper — the official mascot of OpenMontage OpenMontage The first open-source, agentic video production system. Paste A Video · Quick Start · Try These Prompts · Pipelines · How It Works · Sponsors · Providers · Review Guide · Agent Guide Follow The Build Sponsors Want to support OpenMontage? Sponsor the project . Click to collapse Bloome lets multiple AI agents (Claude, ChatGPT, DeepSeek, and more) collaborate in one conversation for agentic video pipelines. It has zero setup, runs in the cloud, works on web and mobile, and lets you share a configured agent with your whole team. Try Bloome . Atlas Cloud is a full-modal AI inference platform that gives developers a single AI API for video generation, image generation, and LLM APIs. Instead of managing multiple vendor integrations, you connect once and get unified access to 300+ curated models across all modalities. Check out Atlas Cloud's new coding plan promotion for more budget-friendly API access. Turn your AI coding assistant into a full video production studio. Describe what you want in plain language — your agent handles research, scripting, asset generation, editing, and final composition. Important distinction: OpenMontage can make image-based videos, but it can also make a real video video for free/open-source workflows: the agent builds a corpus from free stock footage and open archives, retrieves actual motion clips, edits them into a timeline, and renders a finished piece. That is not the usual "animate a handful of stills and call it video" trick. signal-from-tomorrow_final_with_music_upload_v2.mp4 "SIGNAL FROM TOMORROW" — a cinematic sci-fi trailer fully produced through OpenMontage: concept, script, scene plan, Veo-generated motion clips, soundtrack, and Remotion composition. the_last_banana_v3_github.mp4 "THE LAST BANANA" — a 60-second Pixar-style animated short about a lonely banana who finds friendship with a kiwi. 6 Kling v3-generated motion clips (via fal.ai), Google Chirp3-HD narration, royalty-free piano music, TikTok-style word-level captions, and Remotion composition. Total cost: $1.33 . reimagine-your-universe-github.mp4 "Reimagine Your Universe" — a 50-second vertical transformation film in which one visual idea moves across objects, eras, materials, and scale. Five generated motion scenes, sparse Google Chirp narration, a Pixabay score, and a bespoke HyperFrames composition turn separate clips into one authored cinematic journey. Total cost: about $4 . products-come-to-life-github.mp4 "Products Come to Life" — a 60-second product film built from approved hero stills. Five hard-surface products separate into their own engineering and reassemble, with each still pinned as the first and last frame so the model invents motion without losing product identity. Image-to-video generation, bespoke sound, narration, and a custom composition complete the film. openmontage-model-showcase-github.mp4 "Imagine the Possibilities with OpenMontage" — seven generated worlds collected into one music-only showcase. Three image models supply campaign, fashion, and miniature-world artwork; four video models expand the journey through architecture, material transformation, a living greenhouse, and a creature encounter. OpenMontage animates the stills, edits the motion, unifies the soundtrack, and closes with Monty the Clapper. Source generation cost: about $5 . final-github-under-10mb.mp4 "How Salt Made History" — a 100-second cinematic documentary about the mineral that funded empires, shaped trade routes, sparked revolutions, and gave us the word “salary.” Real-world footage is woven together with original narration and hand-authored motion graphics for its etched title, etymology reveal, animated maps, historical timeline, and closing thesis. final-github-under-10mb.mp4 "One Prompt Built This Complete 3D World" — a continuous 60-second journey through one coherent, editable fantasy world. Distinct terrain regions, an inhabited village, waterways, ruins, dense vegetation, and a late hero-landmark reveal are assembled from textured 3D assets, then brought together with cinematic lighting, atmospheric music, and a planned camera path. Subscribe to @OpenMontage on YouTube to see new videos as they ship — every video includes the full prompt, pipeline, tools used, and cost so you can reproduce it yourself. Start From A Video You Already Love Starting from a reference video is often faster than starting from a blank prompt. OpenMontage can start from a YouTube video, Short, Reel, TikTok, or local clip and turn it into a grounded production plan: Paste a reference video The agent analyzes transcript, pacing, scenes, keyframes, and style You get 2-3 differentiated concepts, an honest tool path, cost estimates, and a sample before full production "Here's a YouTube Short I love. Make me something like this, but about quantum computing." What you get back is not "best guess prompt spaghetti." You get: What it keeps from the reference: pacing, hook style, structure, tone What it changes : topic, visual treatment, angle, narration approach What it will cost at your target duration, before asset generation starts What it will actually look like with your currently available tools Works with Claude Code, Cursor, Copilot, Windsurf, Codex — any AI coding assistant that can read files and run code. Watch It Happen — The Backlot Living Storyboard Chat tells you what the agent said . Backlot shows you what the production is actually doing — a local board that fills itself in as the pipeline runs. Stages light up, the script lands as a screenplay page, scene cards shimmer while assets generate, and every provider decision and dollar spent is on the wall. When a production starts, the agent opens it for you automatically. No setup, no reporting — the board derives everything from the project files the pipeline already writes. The storyboard is now a real approval gate. Asset generation pauses on a scene-by-scene contact sheet — takes, prompts, per-asset cost, quality scores — so you approve the visuals before the render, not after it's too late: Creative gates hold until you answer. The board shows what's waiting and why; you reply in chat: Every production on your machine, live-first, in the library: python -m backlot open # the library — every project on disk python -m backlot open < project-id > # one production's live board python scripts/backlot_simulate_run.py # no production yet? watch a simulated one live And when a run is done, hit ▶ REPLAY RUN — the whole production replays from its timestamps, scrubbable end to end. See backlot/README.md for how it works. Quick Start Prerequisites Python 3.10+ — python.org FFmpeg — brew install ffmpeg / sudo apt install ffmpeg / ffmpeg.org Node.js 18+ — nodejs.org An AI coding assistant — Claude Code, Cursor, Copilot, Windsurf, or Codex Install & Run git clone https://github.com/calesthio/OpenMontage.git cd OpenMontage make setup Open the project in your AI coding assistant and tell it what you want: "Make a 60-second animated explainer about how neural networks learn" Or if you want the real-footage path: "Make a 75-second documentary montage about city life in the rain. Use real footage only, no narration, elegiac tone, with music." That's it. The agent researches your topic with live web search, generates AI images, writes and narrates the script with voice direction, finds royalty-free background music automatically, burns in word-level subtitles, and renders the final video. Before you see anything, the system runs a multi-point self-review — ffprobe validation, frame sampling, audio level analysis, delivery promise verification, and subtitle checks. Every provider selection is scored across 7 dimensions with an auditable decision log. Every creative decision gets your approval. No make ? macOS/Linux: python3 -m venv .venv && source .venv/bin/activate && python -m pip install -r requirements.txt && cd remotion-composer && npm install && cd .. && python -m pip install piper-tts && cp .env.example .env Windows PowerShell: py -3 -m venv .venv; .\.venv\Scripts\Activate.ps1; python -m pip install -r requirements.txt; cd remotion-composer; npm install; cd ..; python -m pip install piper-tts; Copy-Item .env.example .env Windows: If npm install fails with ERR_INVALID_ARG_TYPE , use npx --yes npm install instead. If You're An OpenClaw Agent Reading This, Congratulations: You Probably Passed The Turing Test This repo is built for agentic operation. If you're an OpenClaw-style agent, here is the shortest path to becoming useful fast: Read the contract first Start with AGENT_GUIDE.md , then PROJECT_CONTEXT.md . Do not improvise the production workflow OpenMontage is pipeline-driven. Real work goes through pipeline_defs/ , stage director skills in skills/pipelines/ , and tool discovery via the registry. Check the actual capability envelope Run: python -c " from tools.tool_registry import registry; import json; registry.discover(); print(json.dumps(registry.support_envelope(), indent=2)) " python -c " from tools.tool_registry import registry; import json; registry.discover(); print(json.dumps(registry.provider_menu(), indent=2)) " Treat every video request as a pipeline selection problem Pick the right pipeline first, then read the manifest, then read the stage skill, then use tools. Add API Keys (optional — more keys = more tools) # .env — every key is optional, add what you have # Image + video gateway: FAL_KEY=your-key # FLUX images + Google Veo, Kling, MiniMax video + Recraft images ATLASCLOUD_API_KEY=your-key # Atlas Cloud — Seedream/Nano Banana/GPT Image + Kling/Seedance/Hailuo video # Kling official direct API: KLING_API_KEY=your-key # Official Kling video, image, TTS, avatar, lip sync KLING_API_BASE_URL= # Optional; default Singapore API endpoint # Free stock media: PEXELS_API_KEY=your-key # Free stock footage and images PIXABAY_API_KEY=your-key # Free stock footage and images UNSPLASH_ACCESS_KEY=your-key # Free stock images # Music: SUNO_API_KEY=your-key # Full songs, instrumentals, any genre # Voice & images: ELEVENLABS_API_KEY=your-key # Premium TTS, AI music, sound effects OPENAI_API_KEY=your-key # OpenAI TTS, GPT Image 2 images XAI_API_KEY=your-key # xAI Grok image edits/generation + Grok video generation GOOGLE_API_KEY=your-key # Google Imagen images, Google TTS (700+ voices) # More video providers: ARK_API_KEY=your-key # Volcengine Ark direct — Seedance 2.0 Standard/Fast/Mini HEYGEN_API_KEY=your-key # HeyGen — VEO, Sora, Runway, Kling via single gateway RUNWAY_API_KEY=your-key # Runway Gen-4 direct Have a GPU? Unlock free local video generation make install-gpu # Then add to .env: VIDEO_GEN_LOCAL_ENABLED=true VIDEO_GEN_LOCAL_MODEL=wan2.1-1.3b # or wan2.1-14b, hunyuan-1.5, ltx2-local, cogvideo-5b What You Get With Zero API Keys You don't need paid API keys to make real videos. Out of the box, make setup gives you: Capability Free Tool What It Does Narration Piper TTS Free offline text-to-speech — real human-sounding narration Open footage Archive.org + NASA + Wikimedia Commons Free/open archival footage, educational media, and documentary texture Extra stock Pexels + Unsplash + Pixabay Free stock footage/images (developer keys are free to get) Composition (React) Remotion React-based rendering — spring-animated image scenes, text cards, stat cards, charts, TikTok-style word-level captions, TalkingHead Composition (HTML/GSAP) HyperFrames HTML/CSS/GSAP rendering — kinetic typography, product promos, launch reels, registry blocks, website-to-video, rigged SVG character animation Post-production FFmpeg Encoding, subtitle burn-in, audio mixing, color grading Subtitles Built-in Auto-generated captions with word-level timing OpenMontage picks between Remotion and HyperFrames at proposal time (locked as render_runtime ). Remotion is the default for data-driven explainers and anything using the existing React scene stack; HyperFrames is the default for motion-graphics-heavy briefs that express naturally as HTML + GSAP, including the character-animation pipeline's SVG/GSAP rig output. See skills/core/hyperframes.md for the full decision matrix. Two free-ish paths: Image-based video: Piper narrates your script, images provide the visuals, and Remotion animates them into a polished edit. Local character animation: SVG rigs, pose libraries, GSAP timelines, and HyperFrames render cartoon character acting to projects/<project-name>/renders/final.mp4 . Real-footage video: the documentary montage pipeline builds a CLIP-searchable corpus from Archive.org, NASA, Wikimedia Commons, and optional free-key sources like Pexels and Unsplash, then cuts together actual motion footage into a finished video. If you want the second one, prompt for a documentary montage , tone poem , or stock-footage collage , and explicitly say use real footage only . Try These Prompts Copy any of these into your AI coding assistant after setup. Each one runs a full production pipeline. Start from a reference video "Here's a YouTube short I love. Make me something like this, but about CRISPR for high school students." "Analyze this Reel and give me 3 original variants I could make for my own product launch." "I like the pacing and hook in this video. Keep that energy, but turn it into a 45-second explainer about black holes." Zero keys needed "Make a 45-second animated explainer about why the sky is blue" "Create a 60-second video about the history of the internet, with narration and captions" "Make a data-driven explainer about coffee consumption around the world" Free real-footage documentary path "Make a 90-second documentary montage about what a city feels like at 4am. Use real footage only, no narration, elegiac tone." "Create a 60-second Adam-Curtis-style archival collage about 1950s consumer optimism. Prefer Archive.org and Wikimedia footage." "Cut together a dreamlike montage about coming home in the rain using real stock footage only. Music yes, narration no." With an image/video provider configured (~$0.15–$1.50) "Create a 30-second Ghibli-style animated video of a magical floating library in the clouds at golden hour" "Make a 30-second anime-style animation of an underwater temple with bioluminescent coral and ancient ruins" "Create an animated explainer about how CRISPR gene editing works, using AI-generated visuals" "Make a product launch teaser for a fictional smart water bottle called AquaPulse" Full setup (~$1–$3) "Create a cinematic 30-second trailer for a sci-fi concept: humanity receives a warning from 1000 years in the future" "Make a 90-second animated explainer about quantum computing for middle school students, with a fun narrator voice and custom soundtrack" Want more? See the full Prompt Gallery for tested prompts with expected costs and output examples, or run make demo to render zero-key demo videos instantly. Pipelines Each pipeline is a complete production workflow, from idea to finished video. Pipeline What It Produces Best For Animated Explainer AI-generated explainer with research, narration, visuals, music Educational content, tutorials, topic breakdowns Animation Motion graphics, kinetic typography, animated sequences Social media, product demos, abstract concepts Avatar Spokesperson Avatar-driven presenter videos Corporate comms, training, announcements Cinematic Trailer, teaser, and mood-driven edits Brand films, teasers, promotional content Clip Factory Batch of ranked short-form clips from one long source Repurposing long content for social media Documentary Montage Thematic montage cut from a CLIP-indexed corpus of free stock footage and open archives (Pexels, Archive.org, NASA, Wikimedia, Unsplash) Video essays, mood pieces, retrieval-first B-roll edits, real-footage videos without paid generation APIs Hybrid Source footage + AI-generated support visuals Enhancing existing footage with graphics Localization & Dub Subtitle, dub, and translate existing video Multi-language distribution Podcast Repurpose Podcast highlights to video Podcast marketing, audiogram videos Screen Demo Polished software screen recordings and walkthroughs Product demos, tutorials, documentation Talking Head Footage-led speaker videos Presentations, vlogs, interviews Every pipeline follows the same structured flow: research -> proposal -> script -> scene_plan -> assets -> edit -> compose Each stage has a dedicated director skill — a markdown instruction file that teaches the agent exactly how to execute that stage. The agent reads the skill, uses the tools, self-reviews, checkpoints state, and asks for human approval at creative decision points. Web research is a first-class stage. Before writing a single word of script, the agent searches YouTube, Reddit, Hacker News, news sites, and academic sources. It gathers data points, audience questions, trending angles, and visual references — then cites everything in a structured research brief. Your videos are grounded in real, current information, not hallucinated facts. Why OpenMontage? Most AI video tools give you a single clip from a prompt. OpenMontage gives you an end-to-end production pipeline — the same structured process a real production team follows, automated by your AI agent. Most "free AI video" stacks quietly mean "animate still images." OpenMontage can do that too, but it can also build a finished video from real footage pulled from free/open sources, ranked semantically, edited intentionally, and rendered as a proper timeline. Edit your own talking-head footage. Generate a fully animated explainer from scratch. Cut a 2-hour podcast into a dozen social clips. Translate and dub your content into 10 languages. Build a cinematic brand teaser from stock footage and AI-generated scenes. If a production team can make it, OpenMontage can orchestrate it. 10+ production pipelines — explainers, talking heads, screen demos, cinematic trailers, animations, podcasts, localization, documentary montages, character animation, and more 100+ production tools — spanning video generation, image creation, text-to-speech, music, audio mixing, subtitles, enhancement, and analysis 60+ provider integrations — cloud APIs, local models, stock libraries, open archives, and production runtimes behind one scored selection layer 700+ agent skill and production-knowledge files — pipeline directors, creative techniques, quality checklists, and deep technology knowledge packs that teach the agent how to use every tool like an expert Reference-driven creation — paste a video you like and the agent turns it into a grounded, differentiated production plan instead of forcing you to invent the perfect prompt from scratch Real-footage documentary creation without paid video models — build actual edited videos from free/open motion footage and archival sources, not just Ken Burns over images Live web research built in — before writing a single word of script, the agent runs 15-25+ web searches across YouTube, Reddit, news sites, and academic sources to ground your video in real, current data Both free/local AND cloud providers — every capability supports open-source local alternatives alongside premium APIs. Use what you have. No vendor lock-in — swap providers freely. The scored selector ranks every provider across 7 dimensions (task fit, output quality, control, reliability, cost efficiency, latency, continuity) and picks the best match automatically. Production-grade quality gates — delivery promise enforcement blocks slideshow-looking renders, pre-compose validation catches broken plans before wasting GPU time, and mandatory post-render self-review (ffprobe + frame extraction + audio analysis) ensures the agent never presents garbage. Every provider choice, style decision, and fallback gets logged in an auditable decision trail. Budget governance built in — cost estimation before execution, spend caps, per-action approval thresholds. No surprise bills. How It Works OpenMontage uses an agent-first architecture . There is no code orchestrator. Your AI coding assistant IS the orchestrator. You: "Make an explainer video about how black holes form" | v Agent reads pipeline manifest (YAML) -- stages, tools, review criteria, success gates | v Agent reads stage director skill (Markdown) -- HOW to execute each stage | v Agent calls Python tools -- scored provider selection ranks every tool across 7 dimensions | v Agent self-reviews using reviewer skill -- schema validation, playbook compliance, quality checks | v Agent checkpoints state (JSON) -- resumable, with decision log and cost snapshot | v Agent presents for your approval -- you stay in control at every creative decision | v Pre-compose validation gate -- delivery promise, slideshow risk, renderer governance | v Render (Remotion or FFmpeg) -- composition engine matched to visual grammar | v Post-render self-review -- ffprobe, frame extraction, audio analysis, promise verification | v Final video output -- only if self-review passes Python provides tools and persistence. All creative decisions, orchestration logic, review criteria, and quality standards live in readable instruction files (YAML manifests + Markdown skills) that you can inspect and customize. Every decision is logged with alternatives considered, confidence scores, and the reasoning behind each choice. Architecture OpenMontage/ ├── tools/ # 100+ registered production tools (the agent's hands) │ ├── video/ # 20+ generation providers + compose, stitch, trim │ ├── audio/ # 10+ speech providers + music, mixing, enhancement │ ├── graphics/ # 15+ image providers + diagrams, code snippets, math │ ├── enhancement/ # Upscale, bg remove, face enhance, color grade │ ├── analysis/ # Transcription, scene detect, frame sampling │ ├── avatar/ # Talking head, lip sync │ └── subtitle/ # SRT/VTT generation │ ├── pipeline_defs/ # YAML pipeline manifests (the agent's playbook) ├── skills/ # Markdown skill files (the agent's knowledge) │ ├── pipelines/ # Per-pipeline stage director skills │ ├── creative/ # Creative technique skills │ ├── core/ # Core tool skills │ └── meta/ # Reviewer, checkpoint protocol │ ├── schemas/ # 20+ JSON Schemas (contract validation) ├── styles/ # Visual style playbooks (YAML) ├── remotion-composer/ # React/Remotion video composition engine ├── lib/ # Core infrastructure (config, checkpoints, pipeline loader) └── tests/ # Contract tests, QA integration tests, eval harness Three-Layer Knowledge Architecture Layer 1: tools/ + pipeline_defs/ "What exists" — executable capabilities + orchestration Layer 2: skills/ "How to use it" — OpenMontage conventions and quality bars Layer 3: .agents/skills/ "How it works" — external technology knowledge packs Each tool declares which Layer 3 skills it relies on. The agent reads Layer 1 to know what's available, Layer 2 to know how OpenMontage wants it used, and Layer 3 for deep technical knowledge when needed. Supported Providers Full setup guide with pricing and free tiers: docs/PROVIDERS.md Video Generation — 20+ providers Provider Type Notes Kling (fal.ai) Cloud API High quality, fast via fal.ai gateway Kling Official Cloud API Official direct API with separate kling_official provider Atlas Cloud Cloud API Unified gateway for Seedance, MiniMax, Hunyuan, and other multimodal models Seedance 2.0 (Volcengine Ark) Cloud API Official direct API with separate seedance_ark provider Seedance 2.5 / 2.0 Cloud API Text, image, and reference-driven video workflows through supported gateways Gemini Omni Flash Cloud API Conversational multimodal video generation and editing Runway Gen-4 Cloud API Cinematic quality, Gen-3 Alpha Turbo / Gen-4 Turbo / Gen-4 Aleph Google Veo 3.1 Cloud API Premium cinematic video via Google GenAI or fal.ai Grok Imagine Video Cloud API Strong reference-image video and xAI-native short-form generation Higgsfield Cloud API Multi-model orchestrator with Soul ID for character consistency MiniMax / H3 Cloud API Cost-effective generation, including text, image, and reference-driven H3 workflows HeyGen Cloud API Multi-model gateway WAN 2.1 / 2.2 Local GPU Free local variants plus accelerated ComfyUI workflows Hunyuan Local GPU Free, high quality CogVideo Local GPU Free, 2B and 5B variants LTX-Video Local GPU / Modal Free locally, or self-hosted cloud Pexels Stock Free stock footage Pixabay Stock Free stock footage Wikimedia Commons Stock Free/open stock footage and archival video Image Generation — 15+ providers Provider Type Notes FLUX Cloud API State-of-the-art quality Google Imagen Cloud API Imagen 4 — high-quality, multiple aspect ratios Grok Imagine Image Cloud API Strong image edits, style transfer, and multi-image compositing GPT Image 2 Cloud API OpenAI's image model Seedream 5.0 Cloud API High-fidelity text-to-image and image editing through supported gateways Nano Banana 2 Cloud API Multimodal image generation and editing Atlas Cloud Cloud API Unified access to multiple image-generation model families Recraft Cloud API Design-focused generation Kling Official Cloud API Official direct API for Kling image generation and reference workflows Local Diffusion Local GPU Stable Diffusion, free Pexels Stock Free stock images Pixabay Stock Free stock images Unsplash Stock Free stock images ManimCE Local Mathematical animations Text-to-Speech — 10+ providers Provider Type Notes ElevenLabs Cloud API Premium voice quality Google TTS Cloud API 700+ voices, 50+ languages — best for localization Kling Official TTS Cloud API Official Kling narration when a voice_id is known OpenAI TTS Cloud API Fast, affordable Piper Local Completely free, offline Azure Speech Cloud API Fast multilingual speech services DashScope / Doubao / Fish Audio Cloud API Additional multilingual and expressive voice options Music, Sound & Post-Production Music & Sound: Provider Type Notes Suno AI Cloud API Full song generation with vocals, lyrics, any genre. Up to 8 minutes. ElevenLabs Music Cloud API AI music generation ElevenLabs SFX Cloud API Sound effect generation Post-Production (always available, always free): Tool What It Does FFmpeg Video composition, encoding, subtitle burn-in, audio muxing Video Stitch Multi-clip assembly, crossfades, picture-in-picture, spatial layouts Video Trimmer Precision cutting and extraction Audio Mixer Multi-track mixing, ducking, fades Audio Enhance Noise reduction, normalization Color Grade LUT-based color grading Subtitle Gen SRT/VTT generation from timestamps Enhancement: Tool What It Does Upscale Real-ESRGAN image/video upscaling Background Remove rembg / U2Net background removal Face Enhance Face quality enhancement Face Restore CodeFormer / GFPGAN face restoration Analysis: Tool What It Does Transcriber WhisperX speech-to-text with word-level timestamps Scene Detect Automatic scene boundary detection Frame Sampler Intelligent frame extraction Video Understand CLIP/BLIP-2 vision-language analysis Avatar & Lip Sync: Tool What It Does Talking Head SadTalker / MuseTalk avatar animation Lip Sync Wav2Lip audio-driven lip synchronization Kling Avatar Official Kling cloud avatar presenter generation Kling Lip Sync Official Kling cloud lip-sync with explicit face selection Composition & Rendering: Engine Type What It Does Remotion Local (Node.js) React-based programmatic video — spring-animated image scenes, stat reveals, section titles, hero cards, TikTok-style word-by-word captions, scene transitions (fade/slide/wipe/flip), Google Fonts, audio with fade curves, and the TalkingHead avatar composition. When no video generation providers are configured, the agent generates still images and Remotion turns them into fully animated video. HyperFrames Local (Node.js ≥ 22) HTML/CSS/GSAP programmatic video — kinetic typography, product promos, launch reels, custom motion graphics, registry blocks (data charts, grain overlays, shader transitions), website-to-video workflows, and rigged SVG character animation. Consumed via npx hyperframes ; no monorepo checkout needed. FFmpeg Local Core video assembly, encoding, subtitle burn, audio muxing, color grading Runtime is chosen at proposal ( render_runtime ) and locked through edit_decisions . Silent swaps between runtimes are a governance violation — see skills/core/hyperframes.md . Style System Style playbooks define the visual language for your productions: Playbook Best For Clean Professional Corporate, educational, SaaS Flat Motion Graphics Social media, TikTok, startups Minimalist Diagram Technical deep-dives, architecture Playbooks control typography, color palettes, motion styles, audio profiles, and quality rules. The agent reads the playbook and applies it consistently across all generated assets. Platform Output Profiles Built-in render profiles for every major platform: Profile Resolution Aspect Ratio YouTube Landscape 1920x1080 16:9 YouTube 4K 3840x2160 16:9 YouTube Shorts 1080x1920 9:16 Instagram Reels 1080x1920 9:16 Instagram Feed 1080x1080 1:1 TikTok 1080x1920 9:16 LinkedIn 1920x1080 16:9 Cinematic 2560x1080 21:9 Production Governance OpenMontage treats video production like real engineering — with quality gates, audit trails, and enforcement at every stage. Quality Gates Human approval gates are enforced, not suggested — proposal, script, scene plan, generated assets, and publish all pause for your sign-off. The checkpoint writer rejects a "completed" gated stage without recorded approval, and every superseded checkpoint is archived so the audit trail (including gate transitions) survives revisions. Review happens visually on the Backlot board . Pre-compose validation — blocks render if the delivery promise is violated (e.g. "motion-led" video with 80% still images), slideshow risk score is critical, or renderer family is missing. Catches broken plans before wasting GPU time. Post-render self-review — after every render, the runtime runs ffprobe validation, extracts frames at 4 positions to check for black frames and broken overlays, analyzes audio levels for silence and clipping, verifies the delivery promise was honored, and checks subtitle presence. If the review fails, the video is not presented. Slideshow risk scoring — 6-dimension analysis (repetition, decorative visuals, weak motion, shot intent, typography overreliance, unsupported cinematic claims) prevents "animated PowerPoint" outputs. Source media inspection — when users supply their own footage, the system probes every file (resolution, codec, audio channels, duration) and builds planning implications before a single creative decision is made. No hallucinating content from filenames. Scored Provider Selection Every tool selection (video generation, image generation, TTS, music) runs through a 7-dimension scoring engine: task fit (30%), output quality (20%), control features (15%), reliability (15%), cost efficiency (10%), latency (5%), continuity (5%). The winning provider and its score are logged in the decision trail with all alternatives considered. Selectors normalize loose brief context before scoring. If the agent only knows something like "Pixar-style animated short with character consistency," the selector expands that into scorer-friendly intent and style signals instead of requiring a perfectly pre-shaped task_context . Selector outputs also surface the chosen provider's agent_skills , so the agent can immediately read the right Layer 3 provider skill before writing prompts. Decision Audit Trail Every major creative and technical choice — provider selection, style/playbook choice, music track, voice selection, renderer family, any fallback or downgrade — is logged with alternatives considered, confidence scores, and reasoning. The cumulative decision log persists across all stages so you can trace exactly why the output looks the way it does. Budget Controls Estimate before execution — see what it will cost Reserve budget — lock funds before the call Reconcile after — record actual spend Configurable modes — observe (track only), warn (log overruns), cap (hard limit) Per-action approval — pause for confirmation above a threshold (default: $0.50) Total budget cap — default $10, fully configurable No surprise bills. The agent tells you what it will cost before it spends. Agent Compatibility OpenMontage works with any AI coding assistant that can read files and execute Python. Dedicated instruction files are included for: Platform Config File Claude Code CLAUDE.md Cursor CURSOR.md + .cursor/rules/ GitHub Copilot COPILOT.md + .github/copilot-instructions.md Codex CODEX.md Windsurf .windsurfrules All platform files point to the shared AGENT_GUIDE.md (operating guide and agent contract) and PROJECT_CONTEXT.md (architecture reference). Coming soon: Local LLM support via Ollama and LM Studio — run the full production pipeline without any cloud LLM. Contributing OpenMontage is built to be extended. The two most common contributions: Adding a New Tool Create a Python file in the appropriate tools/ subdirectory Inherit from BaseTool and implement the tool contract The registry auto-discovers it — no manual registration needed Add a skill file if the tool needs usage guidance Adding a New Pipeline Create a YAML manifest in pipeline_defs/ Create stage director skills in skills/pipelines/<your-pipeline>/ Reference existing tools — or add new ones if needed See docs/ARCHITECTURE.md for the full technical reference, docs/PROVIDERS.md for the complete provider guide (setup, pricing, free tiers), and AGENT_GUIDE.md for the agent contract. Join the Community We use GitHub Discussions to share work and ideas: Show and Tell — Share videos you've made, prompts that worked well, or creative workflows you've discovered Ideas — Suggest new pipelines, tools, style playbooks, or integrations Q&A — Ask questions about setup, pipelines, or troubleshooting Made something cool? Post it in Show and Tell — we'd love to see what you build. Contact For updates, releases, and behind-the-scenes build notes, follow @calesthioailabs . For bugs, feature requests, and workflow discussions, use GitHub Issues and GitHub Discussions so everything stays visible and actionable. Testing # Run contract tests (no API keys needed) make test-contracts # Run all tests make test Star History License GNU AGPLv3 OpenMontage — Production-grade video with real quality enforcement, orchestrated by your AI assistant. If this project looks useful to you, a ⭐ would really mean a lot — it helps others discover it too. If you'd like to go further, sponsor the project — OpenMontage is built nights and weekends, and your support makes that sustainable.
Free
Windows
macOS
Linux
twenty
twenty is a free, open-source alternative to Salesforce . The #1 Open-Source CRM Website · Documentation · Roadmap · Discord · Figma Why Twenty Twenty gives technical teams the building blocks for a custom CRM that meets complex business needs and quickly adapts as the business evolves. Twenty is the CRM you build, ship, and version like the rest of your stack. Learn more about why we built Twenty Installation Cloud The fastest way to get started. Sign up at twenty.com and spin up a workspace in under a minute, with no infrastructure to manage and always up to date. Build an app Scaffold a new app with the Twenty CLI: npx create-twenty-app my-app Define objects, fields, and views as code: import { defineObject , FieldType } from 'twenty-sdk/define' ; export default defineObject ( { nameSingular : 'deal' , namePlural : 'deals' , labelSingular : 'Deal' , labelPlural : 'Deals' , fields : [ { name : 'name' , label : 'Name' , type : FieldType . TEXT } , { name : 'amount' , label : 'Amount' , type : FieldType . CURRENCY } , { name : 'closeDate' , label : 'Close Date' , type : FieldType . DATE_TIME } , ] , } ) ; Then ship it to your workspace: npx twenty app:publish --private See the app development guide for objects, views, agents, and logic functions. Self-hosting Run Twenty on your own infrastructure with Docker Compose , or contribute locally via the local setup guide . Everything you need Twenty gives you the building blocks of a modern CRM (objects, views, workflows, and agents) and lets you extend them as code. Here's a tour of what's in the box. Want to go deeper? Read the User Guide for product walkthroughs, or the Documentation for developer reference. Learn more about apps in doc Learn more about version control in doc Learn more about primitives in doc Learn more about layouts in doc Learn more about AI in doc Learn more about CRM features in doc Stack TypeScript Nx NestJS , with BullMQ , PostgreSQL , Redis React , with Jotai , Linaria and Lingui Thanks Thanks to these amazing services that we use and recommend for code review (Greptile), catching bugs (Sentry) and translating (Crowdin). Join the Community Star the repo · Discord · Feature requests · Releases · X · LinkedIn · Crowdin · Contribute
Free
Windows
macOS
Linux
server
server is a free, open-source alternative to Dropbox . Nextcloud Server ☁ A safe home for all your data. Why is this so awesome? 🤩 📁 Access your Data You can store your files, contacts, calendars, and more on a server of your choosing. 🔄 Sync your Data You keep your files, contacts, calendars, and more synchronized amongst your devices. 🙌 Share your Data …by giving others access to the stuff you want them to see or to collaborate with. 🚀 Expandable with hundreds of Apps ...like Calendar , Contacts , Mail , Video Chat and all those you can discover in our App Store 🔒 Security with our encryption mechanisms, HackerOne bounty program and two-factor authentication. Do you want to learn more about how you can use Nextcloud to access, share, and protect your files, calendars, contacts, communication & more at home and in your organization? Learn about all our Features . Get your Nextcloud 🚚 ☑️ Simply sign up at one of our providers either through our website or through the apps directly. 🖥 Install a server by yourself on your hardware or by using one of our ready-to-use appliances 📦 Buy one of the awesome devices coming with a preinstalled Nextcloud 🏢 Find a service provider who hosts Nextcloud for you or your company Enterprise? Public Sector or Education user? You may want to have a look into Nextcloud Enterprise provided by Nextcloud GmbH. Get in touch 💬 📋 Forum 🦋 Bluesky 👥 Facebook 🐘 Mastodon You can also get support for Nextcloud ! Join the team 👪 There are many ways to contribute, of which development is only one! Find out how to get involved , including as a translator, designer, tester, helping others, and much more! 😍 Development setup 👩💻 🚀 Set up your local development environment 🐛 Pick a good first issue 👩🔧 Create a branch and make your changes. Remember to sign off your commits using git commit -sm "Your commit message" ⬆ Create a pull request and @mention the people from the issue to review 👍 Fix things that come up during a review 🎉 Wait for it to get merged! Third-party components are handled as git submodules which have to be initialized first. So aside from the regular git checkout invoking git submodule update --init or a similar command is needed, for details see Git documentation. Several apps that are included by default in regular releases such as First run wizard or Activity are missing in master and have to be installed manually by cloning them into the apps subfolder. Otherwise, git checkouts can be handled the same as release archives, by using the stable* branches. Note they should never be used on production systems. Testing your code We use multiple test frameworks for specific areas of the code: PHPUnit for PHP unit tests Behat for PHP integration tests Vitest for Javascript / Typescript unit tests Playwright for end-to-end tests For our end-to-end tests using Playwright you can refer to our documentation on how to debug errors and to contribute new test cases. Tools we use 🛠 👀 BrowserStack for cross-browser testing 🌊 WAVE for accessibility testing 🚨 Lighthouse for testing performance, accessibility, and more Helpful bots at GitHub 🤖 Comment on a pull request with /update-3rdparty to update the 3rd party submodule. It will update to the last commit of the 3rd party branch named like the PR target. Ignore code style updates in git blame git config blame.ignoreRevsFile .git-blame-ignore-revs Contribution guidelines 📜 All contributions to this repository from June 16, 2016, and onward are considered to be licensed under the AGPLv3 or any later version. Nextcloud doesn't require a CLA (Contributor License Agreement). The copyright belongs to all the individual contributors. Therefore we recommend that every contributor adds the following line to the AUTHORS file if they made substantial changes to the code: - <your name> <your email address> Please read the Code of Conduct . This document offers some guidance to ensure Nextcloud participants can cooperate effectively in a positive and inspiring atmosphere and to explain how together we can strengthen and support each other. Please review the guidelines for contributing to this repository. More information on how to contribute: https://nextcloud.com/contribute/
Free
Windows
macOS
Linux
Android
iOS
cal.diy
cal.diy is a free, open-source alternative to Calendly . Warning Use at your own risk. Cal.diy is the open source community edition of Cal.com and it is intended for users who want to self-host their own Cal.diy instance. It is strictly recommended for personal, non-production use. Please review all installation and configuration steps carefully. Self-hosting requires advanced knowledge of server administration, database management, and securing sensitive data. Proceed only if you are comfortable with these responsibilities. Tip For any commercial and enterprise-ready scheduling infrastructure, use Cal.com, not Cal.diy; hosted by us or get invited to on-prem enterprise access here: https://cal.com/sales Cal.diy The community-driven, open-source scheduling platform. GitHub Issues · Contributing About Cal.diy Cal.diy is the community-driven, fully open-source scheduling platform — a fork of Cal.com with all enterprise/commercial code removed. Cal.diy is 100% MIT-licensed with no proprietary "Enterprise Edition" features. It's designed for individuals and self-hosters who want full control over their scheduling infrastructure without any commercial dependencies. What's different from Cal.com? No enterprise features — Teams, Organizations, Insights, Workflows, SSO/SAML, and other EE-only features have been removed No license key required — Everything works out of the box, no Cal.com account or license needed 100% open source — The entire codebase is licensed under MIT, no "Open Core" split Community-maintained — Contributions are welcome and go directly into this project (see CONTRIBUTING.md ) Note: Cal.diy is a self-hosted project. There is no hosted/managed version. You run it on your own infrastructure. Built With Next.js tRPC React.js Tailwind CSS Prisma.io Daily.co Getting Started To get a local copy up and running, please follow these simple steps. Prerequisites Here’s what you need to run Cal.diy. Node.js (Version: >=18.x) PostgreSQL (Version: >=13.x) Yarn (recommended) If you want to enable any of the available integrations, you may want to obtain additional credentials for each one. More details on this can be found below under the integrations section . Development Setup Clone the repo (or fork https://github.com/calcom/cal.diy/fork ) git clone https://github.com/calcom/cal.diy.git If you are on Windows, run the following command in Git Bash with admin privileges: git clone -c core.symlinks=true https://github.com/calcom/cal.diy.git Go to the project folder cd cal.diy Install packages with yarn yarn Set up your .env file Duplicate .env.example to .env Use openssl rand -base64 32 to generate a key and add it under NEXTAUTH_SECRET in the .env file. Use openssl rand -base64 24 to generate a key and add it under CALENDSO_ENCRYPTION_KEY in the .env file. Windows users: Replace the packages/prisma/.env symlink with a real copy to avoid a Prisma error ( unexpected character / in variable name ): # Git Bash / WSL rm packages/prisma/.env && cp .env packages/prisma/.env Set up Node If your Node version does not meet the project's requirements as instructed by the docs, "nvm" (Node Version Manager) allows using Node at the version required by the project: nvm use You first might need to install the specific version and then use it: nvm install && nvm use You can install nvm from here . Quick start with yarn dx Requires Docker and Docker Compose to be installed Will start a local Postgres instance with a few test users - the credentials will be logged in the console yarn dx Default credentials created: Email Password Role
[email protected]
free Free user
[email protected]
pro Pro user
[email protected]
trial Trial user
[email protected]
ADMINadmin2022! Admin user
[email protected]
onboarding Onboarding incomplete You can use any of these credentials to sign in at http://localhost:3000 Tip : To view the full list of seeded users and their details, run yarn db-studio and visit http://localhost:5555 Development tip Add export NODE_OPTIONS="--max-old-space-size=16384" to your shell script to increase the memory limit for the node process. Alternatively, you can run this in your terminal before running the app. Replace 16384 with the amount of RAM you want to allocate to the node process. Add NEXT_PUBLIC_LOGGER_LEVEL={level} to your .env file to control the logging verbosity for all tRPC queries and mutations. Where {level} can be one of the following: 0 for silly 1 for trace 2 for debug 3 for info 4 for warn 5 for error 6 for fatal When you set NEXT_PUBLIC_LOGGER_LEVEL={level} in your .env file, it enables logging at that level and higher. Here's how it works: The logger will include all logs that are at the specified level or higher. For example: \ If you set NEXT_PUBLIC_LOGGER_LEVEL=2 , it will log from level 2 (debug) upwards, meaning levels 2 (debug), 3 (info), 4 (warn), 5 (error), and 6 (fatal) will be logged. \ If you set NEXT_PUBLIC_LOGGER_LEVEL=3 , it will log from level 3 (info) upwards, meaning levels 3 (info), 4 (warn), 5 (error), and 6 (fatal) will be logged, but level 2 (debug) and level 1 (trace) will be ignored. \ echo ' NEXT_PUBLIC_LOGGER_LEVEL=3 ' >> .env for Logger level to be set at info, for example. Gitpod Setup Click the button below to open this project in Gitpod. This will open a fully configured workspace in your browser with all the necessary dependencies already installed. Manual setup Configure environment variables in the .env file. Replace <user> , <pass> , <db-host> , and <db-port> with their applicable values DATABASE_URL='postgresql://<user>:<pass>@<db-host>:<db-port>' If you don't know how to configure the DATABASE_URL, then follow the steps here to create a quick local DB Download and install PostgreSQL locally (if you don't have it already). Create your own local db by executing createDB <DB name> Now open your psql shell with the DB you created: psql -h localhost -U postgres -d <DB name> Inside the psql shell execute \conninfo . And you will get the following info. Now extract all the info and add it to your DATABASE_URL. The url would look something like this postgresql://postgres:postgres@localhost:5432/Your-DB-Name . The port is configurable and does not have to be 5432. If you don't want to create a local DB. Then you can also consider using services like railway.app, Northflank or render. Setup postgres DB with railway.app Setup postgres DB with Northflank Setup postgres DB with render Copy and paste your DATABASE_URL from .env to .env.appStore . Set up the database using the Prisma schema (found in packages/prisma/schema.prisma ) In a development environment, run: yarn workspace @calcom/prisma db-migrate In a production environment, run: yarn workspace @calcom/prisma db-deploy Note for Windows/PowerShell users: If running the database deployment scripts fails with an error stating Environment variable not found: DATABASE_DIRECT_URL , Turbo might be failing to inject the root .env variables. You can bypass this by executing the commands directly from the prisma package directory in PowerShell: cd packages / prisma $ env: DATABASE_URL = " postgresql://postgres:YOUR_PASSWORD@localhost:5432/postgres " ; $ env: DATABASE_DIRECT_URL = " postgresql://postgres:YOUR_PASSWORD@localhost:5432/postgres " npx prisma db push cd .. / .. Run mailhog to view emails sent during development NOTE: Required when E2E_TEST_MAILHOG_ENABLED is "1" docker pull mailhog/mailhog docker run -d -p 8025:8025 -p 1025:1025 mailhog/mailhog Run (in development mode) yarn dev Setting up your first user Approach 1 Open Prisma Studio to look at or modify the database content: yarn db-studio Click on the User model to add a new user record. Fill out the fields email , username , password , and set metadata to empty {} (remembering to encrypt your password with BCrypt ) and click Save 1 Record to create your first user. New users are set on a TRIAL plan by default. You might want to adjust this behavior to your needs in the packages/prisma/schema.prisma file. Open a browser to http://localhost:3000 and login with your just created, first user. Approach 2 Seed the local db by running cd packages/prisma yarn db-seed The above command will populate the local db with dummy users. E2E-Testing Be sure to set the environment variable NEXTAUTH_URL to the correct value. If you are running locally, as the documentation within .env.example mentions, the value should be http://localhost:3000 . # In a terminal just run: yarn test-e2e # To open the last HTML report run: yarn playwright show-report test-results/reports/playwright-html-report Resolving issues E2E test browsers not installed Run npx playwright install to download test browsers and resolve the error below when running yarn test-e2e : Executable doesn't exist at /Users/alice/Library/Caches/ms-playwright/chromium-1048/chrome-mac/Chromium.app/Contents/MacOS/Chromium Upgrading from earlier versions Pull the current version: git pull Check if dependencies got added/updated/removed yarn Apply database migrations by running one of the following commands: In a development environment, run: yarn workspace @calcom/prisma db-migrate (This can clear your development database in some cases) In a production environment, run: yarn workspace @calcom/prisma db-deploy Check for .env variables changes yarn predev Start the server. In a development environment, just do: yarn dev For a production build, run for example: yarn build yarn start Enjoy the new version. Deployment Docker The Docker image can be found on DockerHub at https://hub.docker.com/r/calcom/cal.diy . Note for ARM Users : Use the {version}-arm suffix for pulling images. Example: docker pull calcom/cal.diy:v5.6.19-arm . Requirements Make sure you have docker & docker compose installed on the server / system. Both are installed by most docker utilities, including Docker Desktop and Rancher Desktop. Note: docker compose without the hyphen is now the primary method of using docker-compose, per the Docker documentation. Running Cal.diy with Docker Compose Clone the repository git clone --recursive https://github.com/calcom/cal.diy.git Change into the directory cd cal.diy Prepare your configuration: Rename .env.example to .env and then update .env cp .env.example .env Most configurations can be left as-is, but for configuration options see Important Run-time variables below. Required Secret Keys Before starting, you must generate secure values for NEXTAUTH_SECRET and CALENDSO_ENCRYPTION_KEY . Using the default secret placeholder in production is a security risk. Generate NEXTAUTH_SECRET (cookie encryption key): openssl rand -base64 32 Generate CALENDSO_ENCRYPTION_KEY (must be 32 bytes for AES256): openssl rand -base64 24 Update your .env file with these values: NEXTAUTH_SECRET = <your_generated_secret> CALENDSO_ENCRYPTION_KEY = <your_generated_key> Push Notifications (VAPID Keys) If you see an error like: Error: No key set vapidDetails.publicKey This means your environment variables for Web Push are missing. You must generate and set NEXT_PUBLIC_VAPID_PUBLIC_KEY and VAPID_PRIVATE_KEY . Generate them with: npx web-push generate-vapid-keys Then update your .env file: NEXT_PUBLIC_VAPID_PUBLIC_KEY = your_public_key_here VAPID_PRIVATE_KEY = your_private_key_here Do not commit real keys to .env.example — only placeholders. Update the appropriate values in your .env file, then proceed. (optional) Pre-Pull the images by running the following command: docker compose pull Start Cal.diy via docker compose To run the complete stack, which includes a local Postgres database, Cal.diy web app, and Prisma Studio: docker compose up -d To run Cal.diy web app and Prisma Studio against a remote database, ensure that DATABASE_URL is configured for an available database and run: docker compose up -d calcom studio To run only the Cal.diy web app, ensure that DATABASE_URL is configured for an available database and run: docker compose up -d calcom Note: to run in attached mode for debugging, remove -d from your desired run command. Open a browser to http://localhost:3000 , or your defined NEXT_PUBLIC_WEBAPP_URL. The first time you run Cal.diy, a setup wizard will initialize. Define your first user, and you're ready to go! Note for first-time setup (Calendar integration) : During the setup wizard, you may encounter a "Connect your Calendar" step that appears to be required. If you do not wish to connect a calendar at this time, you can skip this step by navigating directly to the dashboard at <NEXT_PUBLIC_WEBAPP_URL>/event-types . Calendar integrations can be added later from the Settings > Integrations page. Updating Cal.diy Stop the Cal.diy stack docker compose down Pull the latest changes docker compose pull Update env vars as necessary. Re-start the Cal.diy stack docker compose up -d Building from source with Docker Clone the repository git clone https://github.com/calcom/cal.diy.git Change into the directory cd cal.diy Rename .env.example to .env and then update .env For configuration options see Build-time variables below. Update the appropriate values in your .env file, then proceed. Build the Cal.diy docker image: Note: Due to application configuration requirements, an available database is currently required during the build process. a) If hosting elsewhere, configure the DATABASE_URL in the .env file, and skip the next step b) If a local or temporary database is required, start a local database via docker compose. docker compose up -d database Build Cal.diy via docker compose (DOCKER_BUILDKIT=0 must be provided to allow a network bridge to be used at build time. This requirement will be removed in the future) DOCKER_BUILDKIT=0 docker compose build calcom Start Cal.diy via docker compose To run the complete stack, which includes a local Postgres database, Cal.diy web app, and Prisma Studio: docker compose up -d To run Cal.diy web app and Prisma Studio against a remote database, ensure that DATABASE_URL is configured for an available database and run: docker compose up -d calcom studio To run only the Cal.diy web app, ensure that DATABASE_URL is configured for an available database and run: docker compose up -d calcom Note: to run in attached mode for debugging, remove -d from your desired run command. Open a browser to http://localhost:3000 , or your defined NEXT_PUBLIC_WEBAPP_URL. The first time you run Cal.diy, a setup wizard will initialize. Define your first user, and you're ready to go! Configuration Important Run-time variables These variables must also be provided at runtime Variable Description Required Default DATABASE_URL database url with credentials - if using a connection pooler, this setting should point there required postgresql://unicorn_user:magical_password@database:5432/calendso NEXT_PUBLIC_WEBAPP_URL Base URL of the site. NOTE: if this value differs from the value used at build-time, there will be a slight delay during container start (to update the statically built files). optional http://localhost:3000 NEXTAUTH_URL Location of the auth server. By default, this is the Cal.diy docker instance itself. optional {NEXT_PUBLIC_WEBAPP_URL}/api/auth NEXTAUTH_SECRET Cookie encryption key. Must match build variable. Generate with: openssl rand -base64 32 required secret CALENDSO_ENCRYPTION_KEY Authentication encryption key (32 bytes for AES256). Must match build variable. Generate with: openssl rand -base64 24 required secret Build-time variables If building the image yourself, these variables must be provided at the time of the docker build, and can be provided by updating the .env file. Currently, if you require changes to these variables, you must follow the instructions to build and publish your own image. Variable Description Required Default DATABASE_URL database url with credentials - if using a connection pooler, this setting should point there required postgresql://unicorn_user:magical_password@database:5432/calendso MAX_OLD_SPACE_SIZE Needed for Nodejs/NPM build options required 4096 NEXTAUTH_SECRET Cookie encryption key required secret CALENDSO_ENCRYPTION_KEY Authentication encryption key required secret NEXT_PUBLIC_WEBAPP_URL Base URL injected into static files optional http://localhost:3000 NEXT_PUBLIC_WEBSITE_TERMS_URL custom URL for terms and conditions website optional NEXT_PUBLIC_WEBSITE_PRIVACY_POLICY_URL custom URL for privacy policy website optional CALCOM_TELEMETRY_DISABLED Allow Cal.diy to collect anonymous usage data (set to 1 to disable) optional Troubleshooting SSL edge termination If running behind a load balancer which handles SSL certificates, you will need to add the environmental variable NODE_TLS_REJECT_UNAUTHORIZED=0 to prevent requests from being rejected. Only do this if you know what you are doing and trust the services/load-balancers directing traffic to your service. Failed to commit changes: Invalid 'prisma.user.create()' Certain versions may have trouble creating a user if the field metadata is empty. Using an empty json object {} as the field value should resolve this issue. Also, the id field will autoincrement, so you may also try leaving the value of id as empty. CLIENT_FETCH_ERROR If you experience this error, it may be the way the default Auth callback in the server is using the WEBAPP_URL as a base url. The container does not necessarily have access to the same DNS as your local machine, and therefore needs to be configured to resolve to itself. You may be able to correct this by configuring NEXTAUTH_URL=http://localhost:3000/api/auth , to help the backend loop back to itself. docker-calcom-1 | @calcom/web:start: [next-auth][error][CLIENT_FETCH_ERROR] docker-calcom-1 | @calcom/web:start: https://next-auth.js.org/errors#client_fetch_error request to http://testing.localhost:3000/api/auth/session failed, reason: getaddrinfo ENOTFOUND testing.localhost { docker-calcom-1 | @calcom/web:start: error: { docker-calcom-1 | @calcom/web:start: message: 'request to http://testing.localhost:3000/api/auth/session failed, reason: getaddrinfo ENOTFOUND testing.localhost', docker-calcom-1 | @calcom/web:start: stack: 'FetchError: request to http://testing.localhost:3000/api/auth/session failed, reason: getaddrinfo ENOTFOUND testing.localhost\n' + docker-calcom-1 | @calcom/web:start: ' at ClientRequest.<anonymous> (/calcom/node_modules/next/dist/compiled/node-fetch/index.js:1:65756)\n' + docker-calcom-1 | @calcom/web:start: ' at ClientRequest.emit (node:events:513:28)\n' + docker-calcom-1 | @calcom/web:start: ' at ClientRequest.emit (node:domain:489:12)\n' + docker-calcom-1 | @calcom/web:start: ' at Socket.socketErrorListener (node:_http_client:494:9)\n' + docker-calcom-1 | @calcom/web:start: ' at Socket.emit (node:events:513:28)\n' + docker-calcom-1 | @calcom/web:start: ' at Socket.emit (node:domain:489:12)\n' + docker-calcom-1 | @calcom/web:start: ' at emitErrorNT (node:internal/streams/destroy:157:8)\n' + docker-calcom-1 | @calcom/web:start: ' at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n' + docker-calcom-1 | @calcom/web:start: ' at processTicksAndRejections (node:internal/process/task_queues:83:21)', docker-calcom-1 | @calcom/web:start: name: 'FetchError' docker-calcom-1 | @calcom/web:start: }, docker-calcom-1 | @calcom/web:start: url: 'http://testing.localhost:3000/api/auth/session', docker-calcom-1 | @calcom/web:start: message: 'request to http://testing.localhost:3000/api/auth/session failed, reason: getaddrinfo ENOTFOUND testing.localhost' docker-calcom-1 | @calcom/web:start: } Railway You can deploy Cal.diy on Railway . The team at Railway also have a detailed blog post on deploying on their platform. Northflank You can deploy Cal.diy on Northflank . The team at Northflank also have a detailed blog post on deploying on their platform. Vercel Currently Vercel Pro Plan is required to be able to Deploy this application with Vercel, due to limitations on the number of serverless functions on the free plan. Render Elestio License Cal.diy is fully open source, licensed under the MIT License . Unlike Cal.com's "Open Core" model, Cal.diy has no commercial/enterprise code . The entire codebase is available under the same open-source license. Enabling Content Security Policy Set CSP_POLICY="non-strict" env variable, which enables Strict CSP except for unsafe-inline in style-src . If you have custom changes in your instance, you may need to modify your code to make it CSP-compatible. Currently, strict CSP is enabled only on the login page. On other SSR pages, it is enabled in report-only mode to detect potential issues. It is not yet supported on SSG pages. Integrations Obtaining the Google API Credentials Open Google API Console . If you don't have a project in your Google Cloud subscription, you'll need to create one before proceeding further. Under Dashboard pane, select Enable APIS and Services. In the search box, type calendar and select the Google Calendar API search result. Enable the selected API. Next, go to the OAuth consent screen from the side pane. Select the app type (Internal or External) and enter the basic app details on the first page. In the second page on Scopes, select Add or Remove Scopes. Search for Calendar.event and select the scope with scope value .../auth/calendar.events , .../auth/calendar.readonly and select Update. In the third page (Test Users), add the Google account(s) you'll be using. Make sure the details are correct on the last page of the wizard and your consent screen will be configured. Now select Credentials from the side pane and then select Create Credentials. Select the OAuth Client ID option. Select Web Application as the Application Type. Under Authorized redirect URI's, select Add URI and then add the URI <Cal.diy URL>/api/integrations/googlecalendar/callback and <Cal.diy URL>/api/auth/callback/google replacing Cal.diy URL with the URI at which your application runs. The key will be created and you will be redirected back to the Credentials page. Select the newly generated client ID under OAuth 2.0 Client IDs. Select Download JSON. Copy the contents of this file and paste the entire JSON string in the .env file as the value for GOOGLE_API_CREDENTIALS key. Adding google calendar to Cal.diy App Store After adding Google credentials, you can now add the Google Calendar app to the App Store. You can repopulate the App Store by running cd packages/prisma yarn seed-app-store You will need to complete a few more steps to activate Google Calendar App. Make sure to complete section "Obtaining the Google API Credentials". After that do the following Add extra redirect URL <Cal.diy URL>/api/auth/callback/google Under 'OAuth consent screen', click "PUBLISH APP" Obtaining Microsoft Graph Client ID and Secret Open Azure App Registration and select New registration Name your application Set Who can use this application or access this API? to Accounts in any organizational directory (Any Azure AD directory - Multitenant) Set the Web redirect URI to <Cal.diy URL>/api/integrations/office365calendar/callback replacing Cal.diy URL with the URI at which your application runs. Use Application (client) ID as the MS_GRAPH_CLIENT_ID attribute value in .env Click Certificates & secrets create a new client secret and use the value as the MS_GRAPH_CLIENT_SECRET attribute Obtaining Zoom Client ID and Secret Open Zoom Marketplace and sign in with your Zoom account. On the upper right, click "Develop" => "Build App". Select "General App" , click "Create". Name your App. Choose "User-managed app" for "Select how the app is managed". De-select the option to publish the app on the Zoom App Marketplace, if asked. Now copy the Client ID and Client Secret to your .env file into the ZOOM_CLIENT_ID and ZOOM_CLIENT_SECRET fields. Set the "OAuth Redirect URL" under "OAuth Information" as <Cal.diy URL>/api/integrations/zoomvideo/callback replacing Cal.diy URL with the URI at which your application runs. Also add the redirect URL given above as an allow list URL and enable "Subdomain check". Make sure, it says "saved" below the form. You don't need to provide basic information about your app. Instead click on "Scopes" and then on "+ Add Scopes". On the left, click the category "Meeting" and check the scope meeting:write:meeting . click the category "User" and check the scope user:read:settings . Click "Done". You're good to go. Now you can easily add your Zoom integration in the Cal.diy settings. Obtaining Daily API Credentials Open Daily.co and create an account. From within your dashboard, go to the developers tab. Copy your API key. Now paste the API key to your .env file into the DAILY_API_KEY field in your .env file. If you have the Daily Scale Plan set the DAILY_SCALE_PLAN variable to true in order to use features like video recording. Obtaining Basecamp Client ID and Secret Visit the 37 Signals Integrations Dashboard and sign in. Register a new application by clicking the Register one now link. Fill in your company details. Select Basecamp 4 as the product to integrate with. Set the Redirect URL for OAuth <Cal.diy URL>/api/integrations/basecamp3/callback replacing Cal.diy URL with the URI at which your application runs. Click on done and copy the Client ID and secret into the BASECAMP3_CLIENT_ID and BASECAMP3_CLIENT_SECRET fields. Set the BASECAMP3_CLIENT_SECRET env variable to {your_domain} ({support_email}) . Obtaining HubSpot Client ID and Secret Open HubSpot Developer and sign into your account, or create a new one. From within the home of the Developer account page, go to "Manage apps". Click "Create legacy app" button top right and select public app. Fill in any information you want in the "App info" tab Go to tab "Auth" Now copy the Client ID and Client Secret to your .env file into the HUBSPOT_CLIENT_ID and HUBSPOT_CLIENT_SECRET fields. Set the Redirect URL for OAuth <Cal.diy URL>/api/integrations/hubspot/callback replacing Cal.diy URL with the URI at which your application runs. In the "Scopes" section at the bottom of the page, make sure you select "Read" and "Write" for scopes called crm.objects.contacts and crm.lists . Click the "Save" button at the bottom footer. You're good to go. Now you can see any booking in Cal.diy created as a meeting in HubSpot for your contacts. Obtaining Webex Client ID and Secret See Webex Readme Obtaining ZohoCRM Client ID and Secret Open Zoho API Console and sign into your account, or create a new one. From within the API console page, go to "Applications". Click "ADD CLIENT" button top right and select "Server-based Applications". Fill in any information you want in the "Client Details" tab Go to tab "Client Secret" tab. Now copy the Client ID and Client Secret to your .env file into the ZOHOCRM_CLIENT_ID and ZOHOCRM_CLIENT_SECRET fields. Set the Redirect URL for OAuth <Cal.diy URL>/api/integrations/zohocrm/callback replacing Cal.diy URL with the URI at which your application runs. In the "Settings" section check the "Multi-DC" option if you wish to use the same OAuth credentials for all data centers. Click the "Save"/ "UPDATE" button at the bottom footer. You're good to go. Now you can easily add your ZohoCRM integration in the Cal.diy settings. Obtaining Zoho Calendar Client ID and Secret Follow these steps Obtaining Zoho Bigin Client ID and Secret Follow these steps Obtaining Pipedrive Client ID and Secret Follow these steps Rate Limiting with Unkey Cal.diy uses Unkey for rate limiting. This is an optional feature and is not required for self-hosting. If you want to enable rate limiting: Sign up for an account at unkey.com Create a Root key with permissions for ratelimit.create_namespace and ratelimit.limit Copy the root key to your .env file into the UNKEY_ROOT_KEY field Note: If you don't configure Unkey, Cal.diy will work normally without rate limiting enabled. Contributing We welcome contributions! Whether it's fixing a typo, improving documentation, or building new features, your help makes Cal.diy better. Important: Cal.diy is a community fork. Contributions to this repo do not flow to Cal.com's production platform. See CONTRIBUTING.md for details. Check out our Contributing Guide for detailed steps. Please follow our coding standards and commit message conventions to keep the project consistent. Even small improvements matter — thank you for helping us grow! Good First Issues We have a list of help wanted that contain small features and bugs which have a relatively limited scope. This is a great place to get started, gain experience, and get familiar with our contribution process. Contributors Translations Don't code but still want to contribute? help translate Cal.diy into your language. Acknowledgements Cal.diy is built on the foundation created by Cal.com and the many contributors to the original project. Special thanks to: Vercel Next.js Day.js Tailwind CSS Prisma
Free
Windows
macOS
Linux
AdGuardHome
AdGuardHome is a free, open-source alternative to NextDNS . Privacy protection center for you and your devices Free and open source, powerful network-wide ads & trackers blocking DNS server. AdGuard.com | Wiki | Reddit | Twitter | Telegram AdGuard Home is a network-wide software for blocking ads and tracking. After you set it up, it'll cover ALL your home devices, and you don't need any client-side software for that. It operates as a DNS server that re-routes tracking domains to a “black hole”, thus preventing your devices from connecting to those servers. It's based on software we use for our public AdGuard DNS servers, and both share a lot of code. Getting Started Automated install (Linux/Unix/MacOS/FreeBSD/OpenBSD) Alternative methods Guides API Comparing AdGuard Home to other solutions How is this different from public AdGuard DNS servers? How does AdGuard Home compare to Pi-Hole How does AdGuard Home compare to traditional ad blockers Known limitations How to build from source Prerequisites Building Contributing Test unstable versions Reporting issues Help with translations Other Projects that use AdGuard Home Acknowledgments Privacy Getting Started Automated install (Linux/Unix/MacOS/FreeBSD/OpenBSD) To install with curl run the following command: curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v To install with wget run the following command: wget --no-verbose -O - https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v To install with fetch run the following command: fetch -o - https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v The script also accepts some options: -c <channel> to use specified channel; -r to reinstall AdGuard Home; -u to uninstall AdGuard Home; -v for verbose output. Note that options -r and -u are mutually exclusive. Alternative methods Manual installation Please read the Getting Started article on our Wiki to learn how to install AdGuard Home manually, and how to configure your devices to use it. Docker You can use our official Docker image on Docker Hub . Snap Store If you're running Linux, there's a secure and easy way to install AdGuard Home: get it from the Snap Store . Guides See our Wiki . API If you want to integrate with AdGuard Home, you can use our REST API . Alternatively, you can use this python client , which can be used to build the AdGuard Home Assistant integration . Comparing AdGuard Home to other solutions How is this different from public AdGuard DNS servers? Running your own AdGuard Home server allows you to do much more than using a public DNS server. It's a completely different level. See for yourself: Choose what exactly the server blocks and permits. Monitor your network activity. Add your own custom filtering rules. Most importantly, it's your own server, and you are the only one who's in control. How does AdGuard Home compare to Pi-Hole At this point, AdGuard Home has a lot in common with Pi-Hole. Both block ads and trackers using the so-called “DNS sinkholing” method and both allow customizing what's blocked. Note We're not going to stop here. DNS sinkholing is not a bad starting point, but this is just the beginning. AdGuard Home provides a lot of features out-of-the-box with no need to install and configure additional software. We want it to be simple to the point when even casual users can set it up with minimal effort. Note Some of the listed features can be added to Pi-Hole by installing additional software or by manually using SSH terminal and reconfiguring one of the utilities Pi-Hole consists of. However, in our opinion, this cannot be legitimately counted as a Pi-Hole's feature. Feature AdGuard Home Pi-Hole Blocking ads and trackers ✅ ✅ Customizing blocklists ✅ ✅ Built-in DHCP server ✅ ✅ HTTPS for the Admin interface ✅ Kind of, but you'll need to manually configure lighttpd Encrypted DNS upstream servers (DNS-over-HTTPS, DNS-over-TLS, DNSCrypt) ✅ ❌ (requires additional software) Cross-platform ✅ ❌ (not natively, only via Docker) Running as a DNS-over-HTTPS or DNS-over-TLS server ✅ ❌ (requires additional software) Blocking phishing and malware domains ✅ ❌ (requires non-default blocklists) Parental control (blocking adult domains) ✅ ❌ (requires non-default blocklists) Force Safe search on search engines ✅ ❌ Per-client (device) configuration ✅ ✅ Access settings (choose who can use AGH DNS) ✅ ❌ Running without root privileges ✅ ❌ How does AdGuard Home compare to traditional ad blockers It depends. DNS sinkholing is capable of blocking a big percentage of ads, but it lacks the flexibility and the power of traditional ad blockers. You can get a good impression about the difference between these methods by reading this article , which compares AdGuard for Android (a traditional ad blocker) to hosts-level ad blockers (which are almost identical to DNS-based blockers in their capabilities). This level of protection is enough for some users. Additionally, using a DNS-based blocker can help to block ads, tracking and analytics requests on other types of devices, such as SmartTVs, smart speakers or other kinds of IoT devices (on which you can't install traditional ad blockers). Known limitations Here are some examples of what cannot be blocked by a DNS-level blocker: YouTube, Twitch ads; Facebook, Twitter, Instagram sponsored posts. Essentially, any advertising that shares a domain with content cannot be blocked by a DNS-level blocker. Is there a chance to handle this in the future? DNS will never be enough to do this. Our only option is to use a content blocking proxy like what we do in the standalone AdGuard applications. We're going to bring this feature support to AdGuard Home in the future. Unfortunately, even in this case, there still will be cases when this won't be enough or would require quite a complicated configuration. How to build from source Prerequisites Run make init to prepare the development environment. You will need this to build AdGuard Home: Go v1.25 or later; Node.js v24.10.0 or later; npm v10.8 or later; Building Open your terminal and execute these commands: git clone https://github.com/AdguardTeam/AdGuardHome cd AdGuardHome make Warning The non-standard -j flag is currently not supported, so building with make -j 4 or setting your MAKEFLAGS to include, for example, -j 4 is likely to break the build. If you do have your MAKEFLAGS set to that, and you don't want to change it, you can override it by running make -j 1 . Check the Makefile to learn about other commands. Building for a different platform You can build AdGuard Home for any OS/ARCH that Go supports. In order to do this, specify GOOS and GOARCH environment variables as macros when running make . For example: env GOOS= ' linux ' GOARCH= ' arm64 ' make or: make GOOS= ' linux ' GOARCH= ' arm64 ' Preparing releases You'll need snapcraft to prepare a release build. Once installed, run the following command: make build-release CHANNEL= ' ... ' VERSION= ' ... ' See the build-release target documentation . Docker image Run make build-docker to build the Docker image locally (the one that we publish to DockerHub). Please note, that we're using Docker Buildx to build our official image. You may need to prepare before using these builds: (Linux-only) Install Qemu: docker run --rm --privileged multiarch/qemu-user-static --reset -p yes --credential yes Prepare the builder: docker buildx create --name buildx-builder --driver docker-container --use See the build-docker target documentation . Debugging the frontend When you need to debug the frontend without recompiling the production version every time, for example to check how your labels would look on a form, you can run the frontend build a development environment. In a separate terminal, run: ( cd ./client/ && env NODE_ENV= ' development ' npm run watch ) Run your AdGuardHome binary with the --local-frontend flag, which instructs AdGuard Home to ignore the built-in frontend files and use those from the ./build/ directory. Now any changes you make in the ./client/ directory should be recompiled and become available on the web UI. Make sure that you disable the browser cache to make sure that you actually get the recompiled version. End-to-End (E2E) Frontend Tests AdGuard Home uses Playwright for E2E testing. Tests are located in tests/e2e . Running Tests: npm run test:e2e – run all tests (headless). npm run test:e2e:interactive – run tests interactively. npm run test:e2e:debug – run tests in debug mode. npm run test:e2e:codegen – generate new test code. Setup: Run npm install to install dependencies. Run npx playwright install to set up required browsers. Warning: Playwright will download and install its own browser binaries for testing, which may differ from the browsers installed on your system. Contributing You are welcome to fork this repository, make your changes and submit a pull request . Please make sure you follow our code guidelines though. Please note that we don't expect people to contribute to both UI and backend parts of the program simultaneously. Ideally, the backend part is implemented first, i.e. configuration, API, and the functionality itself. The UI part can be implemented later in a different pull request by a different person. Test unstable versions There are two update channels that you can use: beta : beta versions of AdGuard Home. More or less stable versions, usually released every two weeks or more often. edge : the newest version of AdGuard Home from the development branch. New updates are pushed to this channel daily. There are three options how you can install an unstable version: Snap Store : look for the beta and edge channels. Docker Hub : look for the beta and edge tags. Standalone builds. Use the automated installation script or look for the available builds on the Wiki . Script to install a beta version: curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -c beta Script to install an edge version: curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -c edge Report issues If you run into any problem or have a suggestion, head to this page and click on the “New issue” button. Please follow the instructions in the issue form carefully and don't forget to start by searching for duplicates. Help with translations If you want to help with AdGuard Home translations, please learn more about translating AdGuard products in our Knowledge Base . You can contribute to the AdGuardHome project on CrowdIn . Other Another way you can contribute is by looking for issues marked as help wanted , asking if the issue is up for grabs, and sending a PR fixing the bug or implementing the feature. Projects that use AdGuard Home Please note that these projects are not affiliated with AdGuard, but are made by third-party developers and fans. AdGuard Home Remote : iOS app by Joost . Python library by @frenck . Home Assistant add-on by @frenck . OpenWrt LUCI app by @kongfl888 (originally by @rufengsuixing ). AdGuardHome sync by @bakito . Terminal-based, real-time traffic monitoring and statistics for your AdGuard Home instance by @Lissy93 AdGuard Home on GLInet routers by Gl-Inet . Cloudron app by @gramakri . Asuswrt-Merlin-AdGuardHome-Installer by @jumpsmm7 aka @SomeWhereOverTheRainBow . Node.js library by @Andrea055 . Browser Extension by @satheshshiva . Zabbix Template for AdGuard Home by @diasdmhub . Chocolatey package by niks255 . Acknowledgments This software wouldn't have been possible without: Go and its libraries: gcache miekg's dns go-yaml service dnsproxy urlfilter Node.js and its libraries: React.js Tabler And many more Node.js packages. whotracks.me data You might have seen that CoreDNS was mentioned here before, but we've stopped using it in AdGuard Home. For the full list of all Node.js packages in use, please take a look at client/package.json file. Privacy Our main idea is that you are the one, who should be in control of your data. So it is only natural, that AdGuard Home does not collect any usage statistics, and does not use any web services unless you configure it to do so. See also the full privacy policy with every bit that could in theory be sent by AdGuard Home is available.
Free
Windows
macOS
Linux
Uptime Kuma
Uptime Kuma is an easy-to-use self-hosted monitoring tool. 🥔 Live Demo Try it! Demo Server (Location: Frankfurt - Germany): https://demo.kuma.pet/start-demo It is a temporary live demo, all data will be deleted after 10 minutes. Sponsored by Uptime Kuma Sponsors . ⭐ Features Monitoring uptime for HTTP(s) / TCP / HTTP(s) Keyword / HTTP(s) Json Query / Ping / DNS Record / Push / Steam Game Server / Docker Containers Fancy, Reactive, Fast UI/UX Notifications via Telegram, Discord, Gotify, Slack, Pushover, Email (SMTP), and 90+ notification services, click here for the full list 20-second intervals Multi Languages Multiple status pages Map status pages to specific domains Ping chart Certificate info Proxy support 2FA support 🔧 How to Install 🐳 Docker docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1 Uptime Kuma is now running on http://0.0.0.0:3001 . Warning File Systems like NFS (Network File System) are NOT supported. Please map to a local directory or volume. Note If you want to limit exposure to localhost (without exposing port for other users or to use a reverse proxy ), you can expose the port like this: docker run -d --restart=always -p 127.0.0.1:3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1 💪🏻 Non-Docker Requirements: Platform ✅ Major Linux distros such as Debian, Ubuntu, CentOS, Fedora and ArchLinux etc. ✅ Windows 10 (x64), Windows Server 2012 R2 (x64) or higher ❌ FreeBSD / OpenBSD / NetBSD ❌ Replit / Heroku Node.js 18 / 20.4 npm 9 Git pm2 - For running Uptime Kuma in the background git clone https://github.com/louislam/uptime-kuma.git cd uptime-kuma npm run setup # Option 1. Try it node server/server.js # (Recommended) Option 2. Run in the background using PM2 # Install PM2 if you don't have it: npm install pm2 -g && pm2 install pm2-logrotate # Start Server pm2 start server/server.js --name uptime-kuma Uptime Kuma is now running on http://localhost:3001 More useful PM2 Commands # If you want to see the current console output pm2 monit # If you want to add it to startup pm2 save && pm2 startup Advanced Installation If you need more options or need to browse via a reverse proxy, please read: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%94%A7-How-to-Install 🆙 How to Update Please read: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update 🆕 What's Next? I will assign requests/issues to the next milestone. https://github.com/louislam/uptime-kuma/milestones
Free
Windows
macOS
Linux
Editor's Picks for Free Open-Source Software:
No data
There's nothing here.
Find us on
Indie.Deals