Search Results for "headless"

Headless and configurable authentication and user management, including MFA, social login, custom identities and more. Ory Kratos is a fully featured user management system built for the cloud. Control every aspect with a headless API. Ory Kratos comes with support for a wide range of 2FA protocols such as TOTP, FIDO2 & WebAuthn, works with any UI framework, and only a few lines of code are required to get it up and running.

The fun, functional and stateful way to build terminal apps. A Go framework based on The Elm Architecture. Bubble Tea is well-suited for simple and complex terminal applications, either inline, full-window, or a mix of both. Bubble Tea is in use in production and includes a number of features and performance optimizations we’ve added along the way. Among those is a standard framerate-based renderer, a renderer for high-performance scrollable regions which works alongside the main renderer,...

Take the API overhead out of your brain with Daptin. Complete granular access to your data over the network. A single binary to power up your application. Database-backed persistence, 3NF normalized tables. JSON API/GraphQL for CRUD apis. User and group management and access control. Social login with OAuth: tested with google, github, LinkedIn. Actions for abstracting out business flows. Extensive state tracking APIs. Enable Data Auditing from a single toggle. Synchronous Data Exchange with...

Ponzu is a powerful and efficient open-source HTTP server framework and CMS. It provides automatic, free, and secure HTTP/2 over TLS (certificates obtained via Let's Encrypt), a useful CMS and scaffolding to generate content editors, and a fast HTTP API on which to build modern applications. Ponzu is released under the BSD-3-Clause license. With the rise in popularity of web/mobile apps connected to JSON HTTP APIs, better tools to support the development of content servers and management...

...Node.js/Express.js, Python/Django, etc...) and potentially your frontend proxy server (e.g. nginx, traefik, apache, etc...) or even directly to the outside world that does actually nothing but transporting requests and responses as they are except when it detects whitelisted requests according to the config. In that case, Rendora instructs a headless Chrome instance to request and render the corresponding page and then return the server-side rendered page back to the client (i.e. the frontend proxy server or the outside world).