Installation
Installation approach
The platform is being developed to support local deployment on practical hardware rather than requiring a permanent dependency on external AI services. Depending on the environment, that may mean a workstation, a private desktop, a controlled server, or a future distributed node arrangement.
Exact installation steps will evolve as the application matures, but the intended deployment philosophy is already clear: local runtime, user-owned storage, explicit configuration, and operational visibility.
General prerequisites
- A supported operating environment
- Sufficient RAM for the selected local model workload
- Storage for application data, logs, and knowledge assets
- Local model runtime access
- A stable database environment where applicable
- Clear filesystem paths and operational permissions
Deployment posture
FridayLocalAI is being designed for people who want control over where the application runs and how it behaves. That means installation should not feel like surrendering your machine to a mystery wizard. The system should be deployable in a way that remains inspectable and administratively sane.
Future documentation will provide step-by-step instructions for supported environments as those flows are finalized.
Planned deployment targets
Laptop
For lighter local tasks, controlled note-taking, and practical mobility.
Workstation
For more serious local reasoning, artifacts, and larger model workloads.
Private Server
For controlled internal use, persistent runtime, and organizational deployment.
Future Nodes
For distributed or edge deployments with explicit handshake and governance rules.
Current status
This page establishes the intended installation direction of the platform and will be expanded with operational instructions, supported installation flows, runtime dependencies, and environment-specific setup guidance as those procedures are finalized.
For a broader system view, continue to Architecture or Hardware Requirements.