A zero-config, TypeScript-first web framework for developers who value security and performance.
Components are rendered on the server, sending lightweight HTML Redpoint boosts site speed by rendering components server-side and delivering lean HTML to the browser, eliminating any unnecessary JavaScript.
Only the code your import reaches the client, so the payload stays tiny and loads instantly. No more worries about node_modules directory or a heavy package manager - Redpoint is built around Deno's secure URL-based imports.
Ships with no external dependenices, keeping the installation footprint minimal and avoiding version-conflict headaches.
Define reusable layout files and build your own components library with native TypeScript, letting you structure pages consistently while retaining full control over markup and styling.
Protection for your project out of box without complex configurations or external plugins. Redpoint integrates security mechanisms directly into the core; with path-based credentials, rate limits, allowed hosts filtering, and sandbox reliance.
Thanks to the power of Deno, you get TypeScript first-class support with no additional setup; security as a standard with a permission-based architecture leaving you with the final say on all network and file system access in a trusted, restricted sandbox; and removing the need of node_modules and package.json, leaving no legacy overhead and no more dependency hell.
...and more: Web Standards Code Linter Test Runner Code Formatter Standalone Executables
Redpoint was originally developed to establish total ownership and control over the tech stack, ensuring architectural predictability and operational freedom for the groundwork moving forward in SudoVanilla projects.
No. Redpoint relies entirely on the Deno runtime and the way Deno does things. It does not generate or look for a package.json file for configuration or dependency tracking. Instead, the deno.json file is used, read more about it in their documentation.
Redpoint won't generate a node_modules directory. Redpoint is built around Deno, Deno will download and cache dependencies globally in a central system directory, keeping your project directory clean. This behavior can be changed in using the deno.json file by changing the "nodeModulesDir" setting, but not needed by Redpoint.
No. Redpoint is explicitly built for the Deno runtime. Traditional Node.js-based package managers cannot be used to manage Redpoint projects. Global namespaces like "Deno" are used within Redpoint, which won't work with other package managers.
The decision was made to build Redpoint completely in-house on top of Deno to break free from the historical complexities, bloated dependency trees, and configuration fatigue associated with the Node.js system.
Migrating from a Node.js framework to Redpoint is straight-forward, because your modern JavaScript/TypeScript code remains valid. The transition focuses on changing your runtime assumptions and replacing your package management. Explore the documentation for more information on this topic.
You'll only need Deno installed on your system. Supported on macOS, Linux, and Windows.
You can use any databases that has a Deno-compatible driver or a standard Web API. Redpoint won't lock you into a specific database, allowing you to use your preferred storage layer.
You can deploy Redpoint anywhere that supports Deno or Docker containers.
Yes. Redpoint does fully support npm packages thanks to Deno's native compatibility layer. However, the "npm:" prefix is required.
If you encounter issues with the framework itself, you can report bugs and issues to the official repository found on SudoVanilla.