llms.txt
Compare with other sites' llms.txt files →# Windshift
> Windshift is an open-source, self-hosted work management platform and Jira alternative for teams that want project management, test management, time tracking, portals, plugins, and AI features on their own infrastructure.
## Product and Commercial Pages
Core pages for understanding what Windshift is, what it costs, how to install it, and which product areas it covers.
- [Open-Source Jira Alternative | Windshift](https://windshift.sh/): Open-source, self-hosted work management and Jira alternative with boards, milestones, portals, time tracking, and test management on your infrastructure.
- [Connected Delivery Platform, Self-Hosted | Windshift](https://windshift.sh/product): Turn customer demand into planned, validated, reportable delivery with one self-hosted system that keeps decisions, code, evidence, and ownership connected.
- [What Windshift Can Do: Product Tour | Windshift](https://windshift.sh/what-windshift-can-do): See what Windshift can do: customer portals, planning, test management, time tracking, Jira migration, and self-hosting. Follow a job through the product.
- [Integrations: GitHub, GitLab, Gitea & Forgejo | Windshift](https://windshift.sh/integrations): Connect Windshift to GitHub, GitLab, Gitea, Forgejo, or the Omni AI agent. Keep development context on the work item and extend Windshift through its API.
- [Windshift Pricing | Free Self-Hosted Work Management](https://windshift.sh/pricing): Self-host Windshift free with unlimited users and workspaces. Pro will add SAML, SCIM, audit logging, commercial licensing, and priority support.
- [Windshift Pro | Enterprise Controls](https://windshift.sh/pro): Windshift Pro will add SAML, SCIM, multiple identity providers, audit logging, commercial licensing, and priority support to self-hosted Windshift.
- [Download Windshift for Docker, Linux, macOS & Windows](https://windshift.sh/download): Download Windshift, the open-source self-hosted Jira alternative. Run it with Docker, a single binary for Linux, macOS, or Windows, or the native macOS app.
## Comparisons
Side-by-side pages for teams evaluating Windshift as a self-hosted Jira alternative.
- [Open-Source Jira Alternatives Compared (2026) | Windshift](https://windshift.sh/jira-alternatives): Compare six self-hosted Jira alternatives in 2026: Windshift, OpenProject, Plane, Taiga, Redmine, and Focalboard, by Jira fit, migration path, and price.
- [Jira Data Center Migration Journey | Windshift](https://windshift.sh/jira-migration): Plan a Jira Data Center migration to Windshift in six steps, from installation and team evaluation to data migration and adoption.
- [Jira Data Center End of Life 2029 | Windshift](https://windshift.sh/compare/jira-data-center): Jira Data Center reaches end of life on March 28, 2029. Review the timeline, what becomes read-only, migration options, and a self-hosted alternative.
- [Self-Hosted Jira Cloud Alternative | Windshift](https://windshift.sh/compare/jira-cloud): Compare Windshift with Jira Cloud on data ownership, release control, pricing, AI services, migration, and the responsibility of self-hosting.
## Guides, Trust, and Company Pages
Useful entry points for documentation, self-hosting, blog content, responsible AI practices, company background, and attribution.
- [Windshift Blog: Guides for Self-Hosted Teams | Windshift](https://windshift.sh/blog): Practical writing on self-hosted work management, Jira alternatives, planning, customer portals, and the decisions behind building Windshift.
- [Windshift Documentation: Setup and Usage Guides | Windshift](https://windshift.sh/docs): Windshift user guides for managing work, boards, backlogs, time tracking, test management, and customer portals on your own infrastructure.
- [About Realigned Technologies | The Team Behind Windshift](https://windshift.sh/about): Meet the team behind Windshift and Story Maps for Jira, used by 3,500+ teams, and learn why we are building a self-hosted Jira alternative.
- [Contact Realigned Technologies about Windshift](https://windshift.sh/contact): Contact Realigned Technologies with questions about Windshift, product evaluation, support, security, privacy, or partnership opportunities.
- [Privacy Policy and Cookie Information | Windshift](https://windshift.sh/privacy): Learn what Realigned Technologies processes when you visit Windshift, contact us, request a demo, or use an account, including cookie-free analytics.
- [Self-Hosted Work Management | Windshift](https://windshift.sh/self-hosting): Run Windshift on infrastructure you choose. Control data location, identity, databases, network boundaries, backups, and the platform lifecycle.
- [AI-Assisted Development Controls | Windshift](https://windshift.sh/responsible-ai): How Windshift verifies AI-assisted code through review, automated checks, supply-chain controls, reproducible builds, and independent penetration testing.
- [Attribution and Open-Source Credits | Windshift](https://windshift.sh/attribution): Open-source attributions, third-party licenses, and credits for the libraries, tools, and assets that Windshift builds on.
## Blog Posts
Long-form notes on self-hosted work management, planning, customer portals, release planning, and AI-assisted software teams.
- [Why Jira teams choose Windshift over OpenProject](https://windshift.sh/blog/why-teams-choose-windshift-over-openproject): Both are open source and self-hosted. Windshift keeps Jira's project model and adds service and test management. OpenProject leads on portfolio planning.
- [Customizable enterprise software: a decade old trap](https://windshift.sh/blog/customizable-enterprise-software-a-decade-old-trap): Vendors sold customization as a way to fit software to the business. It also made leaving expensive, and subscriptions charged for that expense every year.
- [Windshift on a TRMNL e-ink display](https://windshift.sh/blog/windshift-on-a-trmnl-e-ink-display): TRMNL is a simple ePaper display that shows open Windshift items and today's summary. Two small plugins make it work, with nothing to install on the server.
- [How well does Jira translate to Windshift?](https://windshift.sh/blog/how-well-jira-translates-to-windshift): A benchmark of Jira familiarity and migration fidelity, and how Windshift preserves the work patterns and planning data Jira teams rely on.
- [How Windshift's Jira migration assistant works](https://windshift.sh/blog/how-windshift-jira-migration-assistant-works): Connect Jira Cloud or Data Center, select a representative project, review the mapping, and inspect the result before expanding the migration.
- [Coding agents in a local AI loop](https://windshift.sh/blog/local-ai-loop-with-coding-agents): Windshift's runner gives coding agents a controlled path from assigned work to a reviewable pull request on infrastructure you manage.
- [Scrum after coding agents](https://windshift.sh/blog/scrum-in-the-age-of-ai-agents): Sprints still provide a useful cadence, but agent-driven work needs a current record between ceremonies. Windshift keeps the plan and the work in one place.
- [Using coding agents with Windshift](https://windshift.sh/blog/agentic-work-management-with-windshift): Let coding agents read workspace context, turn plans into structured work, and keep the record current through the CLI or MCP.
- [Why Windshift is open source](https://windshift.sh/blog/why-windshift-is-open-source): The AGPL codebase keeps the core product available, while plugins give teams a maintainable place for local extensions without forking the core.
- [Why self-hosted work management is coming back](https://windshift.sh/blog/why-self-hosted-work-management-is-coming-back): Cloud software tied essential systems to vendor pricing, policy, and product decisions. Modern infrastructure makes self-hosting a practical option again.
- [Release planning without spreadsheet drift](https://windshift.sh/blog/release-planning-without-spreadsheet-drift): Connect milestones and iterations to the work itself, so scope and progress stay current as a release changes. No spreadsheet sync to maintain.
- [Customer portals need to connect to the backlog](https://windshift.sh/blog/customer-portals-should-not-create-a-second-backlog): Put external requests in the workspace where delivery happens, with the context teams need and a simpler view for customers.
## User Docs
Product guides for using Windshift day to day.
### Getting Started
- [Overview](https://windshift.sh/docs/01-getting-started/01-overview.md): Windshift is a self-hosted work management platform. Use it to plan, track, and discuss work.
- [Your First Project](https://windshift.sh/docs/01-getting-started/02-your-first-project.md): This walkthrough helps you set up a workspace and start tracking real work.
- [Mobile App](https://windshift.sh/docs/01-getting-started/03-mobile.md): Windshift has a touch-first mobile site at `/m`. You can install it as an app on your phone. It uses the same account, workspaces, and work items as the desktop site.
### Work Management
- [Work Items](https://windshift.sh/docs/02-work-management/01-work-items.md): Work items are the main objects in Windshift. They represent work your team needs to understand, prioritize, and complete. Requirements and defects can also link directly to the test cases and runs that validate them.
- [Boards and Backlogs](https://windshift.sh/docs/02-work-management/02-boards-and-backlogs.md): Use boards and backlogs to manage work from idea to completion.
- [Views](https://windshift.sh/docs/02-work-management/03-views.md): Windshift shows the same work in different views. Each view supports a different task. You can point any view to a workspace, iteration, or collection.
- [Collections](https://windshift.sh/docs/02-work-management/04-collections.md): A collection is a saved query for a set of work items. You write the query in CQL (Collection Query Language). Windshift updates the collection as items are created, edited, or moved.
- [Pages](https://windshift.sh/docs/02-work-management/05-pages.md): Pages are workspace knowledge documents stored in a tree. Use them for specifications, runbooks, decisions, meeting notes, and other information that belongs beside the work.
- [Milestones](https://windshift.sh/docs/02-work-management/06-milestones.md): A milestone is a dated goal that work items roll up into. Use milestones to track releases, deadlines, and launch readiness.
- [Iterations](https://windshift.sh/docs/02-work-management/07-iterations.md): An iteration is a time-boxed period for a set of work. Examples are a sprint, a week, or a release cycle. Each iteration has a start date, an end date, and a status.
- [Teams](https://windshift.sh/docs/02-work-management/08-teams.md): A team is a named group of people used for coverage, on-call, and service levels. Open **Teams** in the main navigation.
### Time Tracking
- [Logging Time](https://windshift.sh/docs/03-time-tracking/01-logging-time.md): A worklog is one time entry. Each worklog belongs to a project and records a date, an interval, a duration, and a description.
- [Projects and Customers](https://windshift.sh/docs/03-time-tracking/02-projects-and-customers.md): Time tracking uses three levels:
### Test Management
- [Test Management](https://windshift.sh/docs/04-test-management/01-test-management.md): Test management lives in the workspace. It connects what you plan to verify with the work items you deliver.
- [Test cases](https://windshift.sh/docs/04-test-management/02-test-cases.md): A test case describes what to check. Each test case belongs to a workspace and can belong to a folder.
- [Test plans](https://windshift.sh/docs/04-test-management/03-test-plans.md): A test plan groups the test cases that run together. Examples are a smoke set, a regression set, or a release candidate checklist.
- [Test runs](https://windshift.sh/docs/04-test-management/04-test-runs.md): A test run executes a plan and records a result for each test case.
- [Test run templates](https://windshift.sh/docs/04-test-management/05-test-run-templates.md): A test run template stores a reusable run configuration. Use a template to start the same run for each release without selecting the plan and options again.
- [Coverage](https://windshift.sh/docs/04-test-management/06-coverage.md): Coverage shows which work items have test cases. Use coverage to find requirements without tests.
- [Reports](https://windshift.sh/docs/04-test-management/07-reports.md): The test report analyzes results across test runs. Open **Reports** in the workspace sidebar.
### Customer Portals
- [Customer Portals](https://windshift.sh/docs/05-customer-portals/01-customer-portals.md): A customer portal is a channel that external users reach without an internal account. Customers submit requests, follow their progress, and browse published articles. Each submission becomes a work item in a workspace.
- [Request types](https://windshift.sh/docs/05-customer-portals/02-request-types.md): A request type is the form a customer completes. Each request type has its own form, routing, and visibility.
- [Email intake](https://windshift.sh/docs/05-customer-portals/03-email-intake.md): Email intake turns incoming mail into work items. Customers can send a request by email, and their replies stay on the same ticket.
- [Customers and organisations](https://windshift.sh/docs/05-customer-portals/04-customers-and-organisations.md): A portal customer is an external user. Customers belong to customer organisations. Organisations group the contacts and requests for one client or department.
- [Request sharing](https://windshift.sh/docs/05-customer-portals/05-request-sharing.md): A portal customer can share a request with the other contacts in the customer organisation. Sharing is off by default. A global administrator enables it for each organisation.
- [Support queue](https://windshift.sh/docs/05-customer-portals/06-support-queue.md): The support queue is a workspace view for the requests that arrive from portals and email. It collects the open tickets that need an agent.
- [Service levels](https://windshift.sh/docs/05-customer-portals/07-service-levels.md): Service levels define the response and resolution targets for the work in a workspace. Windshift evaluates the targets on the work item facts, so a cycle starts, pauses, and stops in the same write that changed the item.
### Admin
- [AI Features](https://windshift.sh/docs/06-admin/01-ai-features.md): Windshift includes optional AI features for planning, summarizing, and organizing work. A workspace administrator connects a language model once. The features then appear throughout the workspace.
- [Coding Agents and Agent Studio](https://windshift.sh/docs/06-admin/02-coding-agents.md): Agent Studio is the workspace catalog for Standard and Coding agents. Workspace administrators create agents, validate their dependencies, test them privately, and review their runs in one place.
- [Global Permissions](https://windshift.sh/docs/06-admin/03-global-permissions.md): Global permissions control actions that reach across a Windshift instance. Examples include creating a workspace, managing the user directory, and publishing a board.
- [Custom Fields](https://windshift.sh/docs/06-admin/04-custom-fields.md): Custom fields store extra data on work items. You define a field once for the whole instance. Then add it to a screen so it appears on item forms.
- [Screens](https://windshift.sh/docs/06-admin/05-screens.md): A screen is a field layout. Screens control which fields appear when a person creates, edits, or views a work item, and in which order.
- [Configuration Sets](https://windshift.sh/docs/06-admin/06-configuration-sets.md): A configuration set bundles the structure and process that workspaces use. It combines a workflow, screens, item types, priorities, and optional governance rules.
- [Item Types, Hierarchy Levels, and Priorities](https://windshift.sh/docs/06-admin/07-item-types-hierarchy-and-priorities.md): These catalogs define what work items look like. Only system administrators can manage them.
- [Statuses and Workflows](https://windshift.sh/docs/06-admin/08-statuses-and-workflows.md): Statuses and workflows define how work moves. Only system administrators can manage them.
- [Users and Groups](https://windshift.sh/docs/06-admin/09-users-and-groups.md): Users are the people who can sign in to Windshift. Groups collect users so you can grant permissions and workspace roles to many people at once.
- [Workspace Roles](https://windshift.sh/docs/06-admin/10-workspace-roles.md): A workspace role is a named set of permissions inside one workspace. Roles decide what a member can do with work in that workspace.
- [Security](https://windshift.sh/docs/06-admin/11-security.md): The Security page controls feature access, agent service accounts, and sign-in. Only system administrators can change these settings.
- [Notification Settings](https://windshift.sh/docs/06-admin/12-notification-settings.md): A notification setting is a named set of rules that decide which events send notifications and who receives them. A configuration set assigns one notification setting to a workspace.
- [Email Templates](https://windshift.sh/docs/06-admin/13-email-templates.md): Windshift sends transactional emails, such as invitations, portal sign-in links, and batched notifications. You can change the subject and body of each email.
- [Condition Sets](https://windshift.sh/docs/06-admin/14-condition-sets.md): A condition set adds rules to the transitions of one workflow. The rules decide who can use each transition and under what conditions. Use condition sets to control how work flows, not only where it can go.
- [Approval Sets](https://windshift.sh/docs/06-admin/15-approval-sets.md): An approval set adds a decision step to a status. When an item enters a status with an approval set, Windshift opens an approval request. The item cannot leave that status until the approval completes.
### Using Windshift
- [Profile and Security](https://windshift.sh/docs/07-using-windshift/01-profile-and-security.md): Your profile and security settings are personal. They apply to your account, not to a workspace. Open your avatar menu, then **Profile** or **Security**.
- [Notifications](https://windshift.sh/docs/07-using-windshift/02-notifications.md): Windshift notifies you about activity on work you care about. Open the bell in the sidebar to see recent notifications, or open the full notifications page.
- [Search](https://windshift.sh/docs/07-using-windshift/03-search.md): Search finds work items across all workspaces. Open **Search** in the sidebar, or open the command palette and select **Search**.
- [Command Palette and Shortcuts](https://windshift.sh/docs/07-using-windshift/04-command-palette-and-shortcuts.md): The command palette is a search box for actions and navigation. Open it with **Cmd+K** (macOS) or **Ctrl+K** (Windows and Linux), or press **Space** twice.
### Platform
- [Actions](https://windshift.sh/docs/08-platform/01-actions.md): An action automates a workflow with a trigger and a flow of steps. Actions run inside one workspace. Open a workspace and select **Actions**, or open workspace settings and select **Actions**.
- [Analytics](https://windshift.sh/docs/08-platform/02-analytics.md): Analytics shows delivery health and flow for a workspace, without requiring iterations. Open a workspace and select **Analytics**.
- [Assets](https://windshift.sh/docs/08-platform/03-assets.md): Assets track the things work is about, such as devices, services, or locations. Open **Assets** in the main navigation.
- [SCM Integrations](https://windshift.sh/docs/08-platform/04-scm-integrations.md): Windshift connects to source control providers so work items link to branches, commits, and pull requests. A system administrator configures providers under **Admin > Integrations & Links > SCM Providers**.
## Self-hosting Guide
Deployment, configuration, C
