Save scaling data to our db

Currently we updating and retrieving the scaling and limits data directly from the server itself. Instead of the save the data to our services collection. While updating we need to update in the server and as well as in our services collection. While retrieving the data get directly from our services collection only, no need to depend on the server.

Dokku External Volume

Project reactflow ui

Expand the reactflow ui to up and take all action buttons into the reactflow. Make sure the reactflow takes full screen.

Ability to buy server on yearly

MCP Agent Skill for Local Developer Workflows

I want a first-class dFlow agent skill for local developer workflows that allows an AI coding agent to manage the full deployment lifecycle (creating orgs/apps, configuring services, managing registries, and inspecting logs) via MCP with OAuth authentication, matching the dashboard's capabilities. This would enable true local project operation where an agent can inspect a repo and configure/deploy to dFlow directly from the developer's machine.

Platform Plan

Service creation based on server capability

User should not able to create new service if the maximum server resources are utilized.

Add support for vertical & horizontal scale

Currently there are no resource management options to deployed service Add support for horizontal-scaling (replica's) 2.1 use dokku ps:scale node-js-app web=1 Add support for vertical-scaling (RAM, CPU) 3.1 use dokku resource:reserve --cpu 100 --memory 100 node-js-app for resource limiting 3.2 use dokku resource:limit --cpu 100 --memory 100 node-js-app for resource reserving

Team members invitation

UI for displaying team members Enable updating team members Roles Create Jwt token for invitation Team members invitation with copy Link and Email Verify tenant and jwt expiration date. Add tenant requested team member Allow admin to remove team members from team

Role-Based Access Control (RBAC) for Team Members

✨ Feature Request: Role-Based Access Control (RBAC) for Team Members Description Introduce Role-Based Access Control (RBAC) to allow workspace admins to manage access permissions for team members. Admins should be able to create custom roles from the dashboard, assigning specific permissions (create, read, update, delete) across various resource types such as: Projects Services Servers Secrets...and more. 💡 Motivation Improve security and control within teams by restricting access to only what's necessary. Prevent accidental modification or deletion of critical resources. ✅ Expected Behavior Admins can create custom roles in the dashboard. For each role, admins can define granular permissions for each collection/resource (CRUD). When inviting a team member, an admin can assign role. UI and API should respect the assigned permissions when rendering options or performing actions. 📌 Notes Consider starting with predefined roles: Admin, Developer, Viewer, and allowing custom roles afterward.

Beszel integration - Install beszel-agent for monitoring & metrics

Integrate Beszel by installing the beszel-agent on the production server and customer machines. This will enable proper monitoring and metrics collection for the deployment. Tasks: Install beszel-agent on the production server Deploy beszel-agent to all customer machines Ensure agent is running and collecting metrics Verify integration with monitoring dashboard This will improve visibility into system health and performance.

Auto-Delete Tailscale Machines When Server is Deleted

Description: When a server is deleted in dFlow, automatically remove the associated Tailscale machine from the Tailscale network. This ensures that no orphaned devices remain connected and avoids potential security or network clutter issues. Acceptance Criteria: Detect Tailscale device(s) linked to a server upon deletion. Automatically remove those devices from Tailscale. Confirm deletion was successful and log the action. Handle cases where the Tailscale device is already missing gracefully. Benefits: Maintains a clean and secure Tailscale network. Prevents unused devices from consuming Tailscale node slots. Reduces manual cleanup after server removal.

Implement Docker Backups via Restic Integration

Description: Add support for automated Docker backups in dFlow using Restic. This will allow users to create secure, incremental, and deduplicated backups of their container volumes, with storage in supported backend providers (S3, etc.). Acceptance Criteria: Detect and list volumes for each Docker service in dFlow. Allow users to configure Restic backup settings (schedule, retention policy, storage backend). Run backups automatically on schedule and allow manual triggers. Support restore operations to the same or a different server. Encrypt backups with user-defined or system-generated keys. Log all backup and restore activities. Benefits: Provides reliable and secure backups for Docker data. Enables quick recovery from data loss or corruption. Minimizes storage costs through Restic’s deduplication.

Migrate Tailwind to v4 and Ensure Consistent UI

Description: Upgrade dFlow’s UI framework from Tailwind CSS v3 to v4, and audit the application to ensure consistent design across all components after migration. This will allow us to take advantage of Tailwind’s latest features, improved performance, and future compatibility. Acceptance Criteria: Upgrade Tailwind from v3 to v4 in the codebase. Update config files and remove deprecated options. Refactor existing components to ensure compatibility with v4 syntax and changes. Audit all pages and components for consistent spacing, typography, and color usage. Ensure dark mode and responsive breakpoints remain functional. Update documentation to reflect any class name or config changes. Benefits: Access to new Tailwind features and performance improvements. Improved long-term maintainability. Consistent and polished UI throughout dFlow.