Building blocks and infrastructure for developers

AgentStack creates an initial agent project and supports an ongoing CLI workflow for adding tools, generating tests, and running the application. It works with multiple model providers and frameworks such as CrewAI and LangGraph, while keeping the generated code open for developers to customize rather than acting as a low-code builder.

Awesome Electron Alternatives is a curated reference for developers evaluating desktop stacks outside Electron. It groups frameworks, runtimes, and GUI toolkits by languages such as C#, C/C++, Java, JavaScript or TypeScript, Python, and others, with short descriptions and license information. The list is useful for forming an initial shortlist when size, memory use, source protection, or an existing web component makes Electron undesirable. It is a directory, not a build tool or a substitute for validating each project’s current support.

flutter-rs provides tooling and a template for building desktop applications with Dart and Rust. After installing Rust, the Flutter SDK, and the cargo-flutter command, developers can create a project, run it with hot reloading, and build an AppImage release. The repository describes the project as work in progress, so it is better suited to experimentation, learning, or contributors willing to handle compatibility issues.

Fusio is a self-hosted, open-source API management platform and gateway written in PHP. It can expose databases, microservices, and custom PHP or JavaScript actions as controlled API products, with a developer portal, SDK generation, usage monitoring, subscription plans, and quotas. Native MCP support can present selected backend actions as tools for AI agents. Docker Compose is the documented quick start, with manual installation also available.

This repository compares Electron, Tauri, NW.js, Wails, NodeGui, Neutralino, Flutter, and .NET MAUI for developers choosing a web-to-desktop stack. Its tables cover platform support, front-end compatibility, updater options, project characteristics, package size, memory use, and other practical differences. Benchmark applications run in GitHub CI to provide like-for-like measurements across frameworks and operating systems. The maintainers note that system load and limited runs introduce error, so the numbers are directional rather than absolute rankings.

Quasar Awesome is a curated directory for developers working with the Quasar framework. It groups official documentation and community links with tutorials, video courses, app extensions, third-party components, development tools, and projects built with Quasar. The list is useful for learning and package discovery, but many external entries are neither created nor maintained by the Quasar team, and their compatibility may target different Quasar versions.

LibVLCSharp exposes VideoLAN's LibVLC engine to .NET and Mono applications across desktop, mobile, server, and Unity environments. Developers can render video, output audio, handle files and network streams, and use encoding or streaming capabilities through a common API, with integrations for frameworks such as WPF, WinForms, MAUI, Avalonia, and Xamarin. Each target also needs the platform-specific native LibVLC package, because the bindings do not include the media engine by themselves.

Elixir Desktop lets Phoenix LiveView developers build native-like local applications for Windows, macOS, Linux, iOS, and Android. It routes window, webview, menu, and notification operations through platform backends, using wxWidgets on desktop, a JSON bridge on mobile, or a browser backend for headless environments. An example application and setup guides provide a starting point. Core desktop and mobile execution works, but complete desktop installer generation, signing, and one-command cross-platform packaging remain roadmap items.

webclaw provides a local-first way to scrape, crawl, map, and extract websites for agents and RAG systems. Its core CLI and MCP workflow can run without an account for many pages, while a hosted API is available for bot-protected sites, JavaScript rendering, asynchronous crawl jobs, search, and production monitoring.

secure-electron-template gives developers a ready starting point for building Electron applications with React, TypeScript, Redux, localization, testing, and packaging already connected. It can be copied through GitHub’s template feature or cloned and run with the included development scripts. The project applies Electron security practices such as context isolation and restricted Node integration, but developers remain responsible for the remote content and permissions their app allows.

level is a convenience package that exposes a common abstract-level interface while selecting classic-level in Node.js and browser-level in web applications. It supports lexicographically ordered keys, batch writes, asynchronous iteration, encodings, and TypeScript declarations. Browser projects normally use it through a bundler such as Browserify, Webpack, or Rollup, while Node.js stores the database in a local directory.

Spectron was a testing framework for Electron applications that combined ChromeDriver with WebdriverIO and provided an Application API for launch and browser-style interaction tests. Its version map ties specific Spectron releases to Electron versions, which matters when maintaining older suites. The project has been officially deprecated since February 1, 2022, so it is mainly relevant to legacy maintenance and migration rather than new test development.

Stlite runs Streamlit applications inside the browser through Pyodide and WebAssembly, removing the need for a Python server. Apps can be mounted with a custom HTML element or JavaScript API, including multiple files, package requirements, configuration, and optional IndexedDB persistence. Because execution stays in a browser sandbox, packages with unsupported native extensions and some blocking Streamlit behaviors will not work as they do in a standard Python environment.

node-hid is a native Node.js module for enumerating, opening, reading from, and writing to USB or Bluetooth HID devices through synchronous or asynchronous APIs. It supports common Windows, macOS, and Linux environments, with prebuilt binaries for many Node.js and Electron combinations. Less common targets may need a source build, and operating systems often restrict access to keyboards, mice, or devices that emulate them; Linux may also require udev rules.

Aurelia 2 is a front-end framework for browser, mobile, and desktop applications that stays close to web standards and favors conventions over configuration. Applications are composed from JavaScript or TypeScript classes paired with HTML templates, and developers can start with the project generator or study the repository's loader and bundler examples. The supplied documentation describes Aurelia 2 as beta software, with untested public API areas and additional breaking changes still possible.

RocketMQ-Rust is a Rust reimplementation of Apache RocketMQ that includes NameServer, Broker, Controller, Proxy, storage, and producer, consumer, and administration components. It can support Rust-native messaging deployments or interoperate with existing Apache RocketMQ Java clients and servers through protocol compatibility. Building the workspace requires Rust 1.85.0 or later.

This chapter-based tutorial incrementally adds Microsoft identity features to an ASP.NET Core web application. It starts with user sign-in, then covers calling Microsoft Graph or your own APIs, role and group authorization, and deployment to Azure, with complete code available for individual stages. The examples address organizational, multitenant, personal-account, and sovereign-cloud scenarios, but exclude daemon applications that call APIs using the app's own identity.

Determine whether a Chrome, Edge, Chromium, or Electron environment can decode or encode HEVC in hardware before shipping video features. The guide maps codec profiles, HDR behavior, operating systems, GPUs, drivers, and browser versions, then shows capability checks with MediaCapabilities, Media Source, WebCodecs, WebRTC, and MediaRecorder. It also documents patches and build paths for custom Chromium or Electron distributions. Results vary substantially by platform and version, so browser branding alone is not a reliable compatibility test.