Weave Code
Goodwork Laravel Package
iluminar/goodwork
Goodwork is a self-hosted project management and collaboration platform built with Laravel and Vue.js. It combines projects, tasks, discussions, calendars, and team communication in one workspace, helping teams plan work, track progress, and stay organized.
Self-hosted app for Time Tracking, Invoice Generation, Project & Client Management, built with Laravel & Filament.
Frequently asked questions about Goodwork
- Can I install iluminar/goodwork with composer require into my existing Laravel project?
- No. Goodwork is a complete Laravel application, not a Composer library, so there is no composer require integration path. You can deploy it as a standalone self-hosted service, fork and customize it in-tree, or study it as a reference implementation for clients, projects, time entries, and invoices.
- Which Laravel and Filament versions does Goodwork support?
- Goodwork is built on Laravel and Filament, but the supported version constraints change over time and will pin your stack. Check the repository's composer.json and release notes for the current Laravel and Filament versions before planning an upgrade. A fork inherits the obligation to track major Filament releases, which have historically involved significant migration work.
- How do I deploy Goodwork to production?
- Treat it like a standard Laravel application: PHP-FPM, MySQL, a queue worker, the scheduler, and persistent storage for invoice PDFs. Because the UI is built with Filament and Livewire, you also need to account for compiled frontend assets and any Node build step if you customize the panels. Run a staging deployment first and exercise the invoice lifecycle end to end.
- Does Goodwork provide a REST API and webhooks for integrations?
- The integration surface must be verified against the current repository because the UI is the primary interface and the API may not be documented or versioned. If you need Goodwork as a capture layer behind your own billing or ERP system, confirm stable API and webhook support before committing. Without that contract, programmatic integration becomes fragile and fork-dependent.
- Is Goodwork suitable for time tracking and invoice generation?
- Goodwork combines time tracking, invoice generation, and project and client management in one self-hosted workspace, so it covers the basic capture and presentation flow. Invoicing carries tax, currency, numbering, and audit-trail requirements that vary by jurisdiction, so confirm those rules are configurable before relying on it. Many teams keep billing as the system of record and use Goodwork only for time capture.
- Who are the main alternatives to Goodwork for self-hosted project management?
- The field is crowded, with SaaS tools like Harvest, Toggl, and Clockify alongside open-source options such as Kimai, Invoice Ninja, and Leantime. Goodwork's strategic case rests more on data residency and self-hosting than on unique capability. Evaluate alternatives against your invoicing and API requirements before choosing.
- How does Goodwork handle multi-tenancy, roles, and SSO?
- Multi-tenancy, team roles, and the authentication model should be reviewed directly in the repository and source code because they are not clearly specified in the project overview. Filament supports socialite and SSO plugins, so OIDC or SAML integration is often possible through configuration or a thin extension. Confirm data isolation behavior before onboarding multiple teams.
- Is Goodwork actively maintained and safe to run in production?
- Goodwork has a solid star count but is backed by a small maintainer group, so release cadence, security response, and test coverage matter more than popularity. Check the CI configuration, test suite breadth, release history over the last twelve months, and the policy for security disclosures. For production use, plan to track upstream releases and have a fallback plan for critical fixes.
- Can I fork Goodwork and customize it for my business?
- Yes, Goodwork is MIT licensed, so forking is permitted, but a fork converts your team into maintainers of a full Laravel and Filament application. You will need to track Laravel upgrades, Filament major-version migrations, and any Node build step for compiled panel assets. Fork only when a hard requirement cannot be met through configuration or a thin extension.
- What should I verify in a two-week spike before adopting Goodwork?
- Deploy the upstream version unmodified, load five to ten real users, and exercise the full invoice lifecycle including PDF generation and numbering. Review authentication, SSO, and data isolation, and confirm PHP 8.2 or 8.3 alignment plus MySQL versus Postgres support. Also verify the API and webhook surface if you plan to integrate with an external billing or ERP system.
Weaver
How can I help you explore Laravel packages today?