hacka.re

Overview

hacka.re is a lightweight serverless web UI which only requires an OpenAI-compatible API for inference. It allows for serverless sharing of strongly encrypted GenAI provider credentials, system prompts, model choice, and conversation history over less secure communication channels.

This architecture allows for serverless GPT's to be shared securely over otherwise insecure channels without touching servers aside from the LLM API endpoint(s) involved for inference. The entire hacka.re site can simply be downloaded and run from disk, or extended and re-published freely as it is licensed under the MIT No Attribution license.

The name "hacka.re" comes from "hackare" (the Swedish word for "hacker"), reflecting the project's ethos: a tool built by hackers, for hackers. The tagline "För hackare, av hackare" translates to "for hackers, by hackers."

Unlike many commercial chat interfaces, hacka.re prioritizes user privacy by storing all data locally in your browser. Your API key and conversation history never leave your device except when making direct requests to your configured API provider. This approach gives users more control over their data while still providing access to state-of-the-art AI models. Note that ALL conversational data is still exposed to your configured API provider's servers and is therefore subject to their privacy policy.

Key Features

Supported Models

hacka.re provides access to all models available through your configured OpenAI-compatible API provider. The interface automatically fetches the latest available models from your provider.

Different API providers offer various models with different capabilities, context window sizes, and performance characteristics. The specific models available to you will depend entirely on which API provider you choose to connect with.

The application's model selector displays all available models from your chosen provider, allowing you to select the one that best fits your current needs.

Technical Architecture

hacka.re is built as a pure client-side application using vanilla JavaScript, HTML, and CSS. This approach eliminates the need for a backend server, ensuring that your data remains on your device.

The application communicates directly with the configured OpenAI-compatible API using your corresponding API key stored in your browser's localStorage. All message processing, including markdown rendering and syntax highlighting, happens locally in your browser.

For detailed information about the technical implementation and architecture, including code examples and security considerations, visit the Architecture page.

Secure Sharing

hacka.re includes a feature to securely share various aspects of your configuration with others through session key-protected URL-based sharing.

Sharing options:

• API Provider: Any OpenAI-compatible API works
• API Key: Share your API key for access to models
• Active Model: Share your selected model preference with automatic fallback if unavailable
• System Prompt: Share your custom system prompt for consistent AI behavior
• Conversation Data: Share recent conversation history with configurable message count

For detailed information about the secure sharing implementation, including code examples, security considerations, and team collaboration features, visit the Architecture page.

Privacy Considerations

Privacy is a core principle of hacka.re. However, it's important to understand the data flow:

• This is a GitHub Pages site - the application is hosted on GitHub's servers
• Stores your API key only in your browser's localStorage
• Keeps conversation history locally on your device
• All chat content is sent to your configured API provider's servers for processing
• Your conversations are subject to your API provider's privacy policy
• Does not use analytics, tracking, or telemetry
• Has no custom backend server that could potentially log your data
• All external js libraries are now hosted locally to prevent third-party CDN connections

While this approach gives you more control over your data than many commercial alternatives, please be aware that your conversation content is processed by your API provider's cloud services. Never share sensitive personal information, credentials, or confidential data in your conversations with not fully trusted API endpoints.

Use Cases

hacka.re can be used in various scenarios, from personal AI assistance to team collaboration:

• Local Development: Download and run the entire application locally without any server setup
• API Provider Flexibility: Use with any OpenAI-compatible API provider
• Secure Team Collaboration: Share API keys, system prompts, and conversations securely with team members
• Cross-Device Usage: Continue conversations across different devices using the secure sharing feature

For detailed examples and step-by-step guides for various use cases, visit the Use Cases page.

Getting Started

To use hacka.re, you'll need an API key from a compatible provider.

Once you have your API key, simply:

1. Visit hacka.re
2. Open settings
3. Select your API provider
4. Paste your API key
5. Select your preferred model
6. Start chatting with LLMs

Your API key and conversations will be saved locally in your browser for future sessions. For more detailed instructions and examples, visit the Use Cases page.

License

hacka.re is released under the MIT No Attribution license, allowing you to freely use, modify, and distribute the software without attribution requirements.