Many project management platforms require a monthly subscription. They typically charge per user, so your bill increases every time another team member needs access.
They also store your project data on their servers, not your own. So what happens to your project and client data if you decide to stop using the service?
Self-hosted project management, like OrbitalWP, gives you more control and flexibility.
OrbitalWP is licensed per site rather than per user, so you can add as many team members as you need without paying an additional fee for each person.
What changes when project management runs inside WordPress?
Imagine a client asks your agency to create a new service page for their website.
The work may include:
- Keyword research
- Writing
- Design
- Development
- Client review
- Revisions
- Publishing
Each stage has an internal procedure explaining how your agency builds service pages. Your team stores these procedures in your company’s WordPress knowledge base.
With a SaaS project management tool, the task may link back to WordPress, a document platform, and other tools. Your team must move between those systems to understand the assignment and complete the work. That means more clicks, passwords, and two-factor authentication prompts.
With OrbitalWP, you can install the plugin on a WordPress subdomain and keep your tasks and procedures in the same place. Create a parent task for the service page, then add subtasks for each stage. Connect the parent task to the related WordPress page and the procedure your team follows. The writer, designer, developer, and reviewer can work from the same task structure without copying the project into several unrelated tools.
When your tasks and procedures live in the same place, they are easier for your team to find, review, and update. The page and procedure related to the work are only a click away.
Whether you work alone or manage a team, you can use the view that fits the way you work.
- Timeline View helps you review deadlines
- Board View gives you a visual overview for planning or weekly meetings
- List View keeps tasks in a simple outline
- Calendar View shows what is due next.
Filters also carry across the different task views. You can narrow your tasks by category, tag, assignee, related post, or parent task, then switch between Board, List, Timeline, and Calendar without setting up the filters again.
This is the practical advantage of WordPress-native project management. Your tasks stay connected to the page, post, product, or procedure related to the work.
Control contractor access with OrbitalWP permissions
OrbitalWP lets you configure task permissions at the role, user, and individual task levels. Each gives tighter control over who can see and edit tasks.
Three ways to grant task access
- Role-based permissions establish access for users with a particular WordPress role.
- User-based permissions grant or deny permissions for an individual user.
- Task-specific permissions grant selected users permission to read, edit, approve, manage assignees, or delete a particular task structure.
Give assignees access without full editing
Agency teams change from one project to the next. A writer may work on one client account. A designer may join for two weeks. A client employee may need to approve a deliverable without managing the project.
Giving every person broad access creates unnecessary risk. It also makes the workspace harder to understand.
OrbitalWP resolves access through WordPress role permissions, user-specific permissions, task-specific overrides, ownership, and assignment access. These layers give an agency several ways to match access to a person’s responsibilities.
Assignment is intentionally narrow. An assigned person can read the task and mark it Completed. Assignment alone does not provide general editing, approval, reassignment, or deletion rights.
Return to the service-page project:
The writer can read and complete the writing task.
The project manager can manage assignments and the broader project.
This lets you make someone responsible for a task without treating that person like a project manager.
Permissions can become complex when roles, individual overrides, ownership, assignments, and task-specific access interact. Test important workflows with representative user accounts. Do not assume that hiding a menu item protects the underlying data.
Keep access to past project data
Data control can sound abstract until you need to recover an old project.
Suppose a client leaves after three years. Six months later, you need to confirm which page projects were approved, which tasks were completed, or which procedure was linked to the work.
With a SaaS platform, your ability to answer those questions depends on the vendor’s cancellation, retention, and export policies. Before choosing a platform, ask:
- What happens to our project data when we cancel, and how long can we access it?
- Does the export preserve tasks, custom fields, linked records, and approvals?
- Can we restore the export, or is it only useful as a reference?
- What happens if the vendor changes the product or closes the service?
Many SaaS vendors provide exports and clearly defined retention periods. However, the vendor still controls the system and determines which recovery options are available.
OrbitalWP stores its core project records within your WordPress environment using WordPress records and OrbitalWP’s database tables. You can include the database and related site files in your existing backup, retention, and migration process.
Create and test a recovery plan
Self-hosting does not protect your data automatically. A backup that has never been restored is only an assumption.
Your recovery plan should:
- Include the WordPress database and related site files.
- Store backups separately from the primary server.
- Define how long backups are retained.
- Identify who is responsible for restoring the site.
- Test the restoration process on a regular schedule.
Where can you install OrbitalWP?
Self-hosting does not mean your project system must run on your agency’s public website. You can choose an environment that matches the sensitivity of the work.
Use your existing WordPress site
A smaller team may run OrbitalWP on its existing agency website. This keeps tasks and related WordPress content in the same installation.
This setup requires careful user permissions and privacy settings. Internal tasks should not be treated like ordinary public content.
Use a dedicated WordPress subdomain
An agency can create a separate WordPress installation such as tasks.example.com or work.example.com.
This separates the agency’s marketing website from its procedures, projects, contractor accounts, and task data. The project environment can have its own users, security rules, and maintenance schedule.
A dedicated subdomain is still normally reachable from the internet. A login page by itself does not make the server private.
Use a private WordPress or intranet installation
Some client work may justify running WordPress and OrbitalWP on a private server behind a company firewall. Employees could access the installation through the internal network or an approved VPN.
In this context, “local WordPress” should mean a managed private environment, not an installation running on one employee’s laptop.
A private installation can reduce public exposure, but it does not automatically make the system secure or compliant with legal and industry requirements. The organization still needs least-privilege accounts, strong authentication, updates, network controls, monitoring, and a tested recovery process.
Self-hosting gives you choices. Your agency is still responsible for choosing and maintaining the right environment.
Self-hosting does not mean complete isolation
Self-hosting keeps your task data inside your own WordPress database. It does not mean the site runs in total isolation. A few ordinary connections still happen.
OrbitalWP contacts OrbitalWP’s licensing service to verify your license and check for plugin updates. The check verifies your site and license key, not the contents of your tasks.
Task notifications go out through your site’s email system. That covers new assignments, due dates, and completion/approval status.
By default, WordPress hands these emails to your server’s built-in mail function, which many hosts deliver poorly or block outright. Because of this, most agencies connect an SMTP or transactional email provider, Postmark and SendGrid are common choices, to improve delivery. Once connected, that provider processes the content of every notification, including task titles and any client names mentioned in them.
None of this is specific to OrbitalWP. It’s true of almost any WordPress site handling client work. The difference with a self-hosted tool is that you control what connects to your site and can review each connection yourself, rather than trusting a vendor’s infrastructure decisions on your behalf.
Compare the full cost of SaaS and self-hosting
Many SaaS project management tools charge a monthly or annual fee for each user. That can work well for a stable internal team, but the total cost increases whenever you add contractors, reviewers, or temporary collaborators.
Consider a team with six employees, four contractors, and two reviewers. If all 12 people need paid access to a tool that costs $12 per user each month, the subscription would cost $144 per month or $1,728 per year.
That is only an example, not the price of a specific platform. Free users, guests, reviewers, and restricted accounts are treated differently by each service. Compare the price of the plan that includes the features and access levels your team needs.
Self-hosting has costs too. Your agency may need to pay for:
- WordPress hosting or internal server resources. You may be able to use existing infrastructure, but a dedicated installation still requires server capacity.
- Backups and off-site storage. Your backup costs will depend on how much data you store, how long you retain it, and where the backups are kept.
- WordPress maintenance. Someone needs to install updates, monitor the site, and fix problems. Existing staff may handle this work, but their time still has value.
- Email delivery. Notification costs depend on whether you use your host’s mail system or an SMTP or transactional email provider.
- Security monitoring. This may be handled through your host, a WordPress security service, or your agency’s existing tools.
- The OrbitalWP license. Standard licenses renew yearly and are priced by site rather than by user. Review the current OrbitalWP pricing when calculating your costs.
The useful comparison is not subscription versus free. It is the cost of the SaaS seats your team needs compared with the cost of operating and maintaining your WordPress environment.
Which option fits your team?
Self-hosted project management is not the right choice for every team. It gives you more control over your users, data, and hosting environment, but your team also becomes responsible for maintaining that environment. You need someone who can manage WordPress updates, backups, security, email delivery, and recovery if something goes wrong.
When SaaS may be the better fit
A SaaS platform may be a better fit when you want the vendor to maintain the application, install updates, operate the infrastructure, and manage availability. It may also make more sense when your workflow depends on built-in team chat, native mobile applications, time tracking, recurring tasks, broad automation, a dedicated client portal, or a large collection of third-party integrations.
When OrbitalWP may be the better fit
OrbitalWP does not currently provide those features. It focuses on project management inside WordPress.
OrbitalWP may be a better fit when your work already centers on WordPress. You can keep tasks connected to the posts, pages, products, and procedures related to the work. You can also manage your WordPress users, database, backups, and hosting environment while controlling which tasks each person can access.
SaaS vs. self-hosted project management
| Question | SaaS may fit better when… | OrbitalWP may fit better when… |
|---|---|---|
| Who should maintain the system? | You want the vendor to operate the application and infrastructure. | Your team already maintains WordPress environments. |
| Where should tasks live? | A separate project management service works well for your team. | Tasks should remain close to WordPress content and procedures. |
| How should access work? | Standard workspace roles and guest options meet your needs. | Access needs to vary by WordPress role, user, assignment, or task. |
| Who should control retention? | The vendor’s export and retention policies meet your requirements. | Your agency wants to manage its own backups and retention process. |
| How should users be priced? | Per-user pricing is predictable and acceptable. | Temporary contributors make seat-based pricing difficult to manage. |
| Where should the system run? | The vendor’s hosting and security model meets your requirements. | You want to choose the host or run WordPress in a private environment. |
Neither approach is automatically better. The decision depends on your workflow, client requirements, technical resources, and the features your team needs.
Test the workflow before you commit
You can learn more from a small test than from a long feature checklist.
Create a representative client project in a safe testing environment:
- Add a real procedure your team follows.
- Create a parent task and several subtasks.
- Connect the work to a related WordPress page or post.
- Add a limited contractor account.
- Assign one task to that contractor.
- Confirm what the contractor can read, complete, edit, approve, reassign, and delete.
- Review the project in Board, List, Timeline, and Calendar views.
This test will show whether WordPress-native project management fits your agency better than a separate SaaS platform.
Frequently asked questions about self-hosted project management
Is self-hosted project management better than SaaS?
It can be a better fit for a WordPress agency that wants control over task data, access, backups, and the project environment. SaaS may be better for a team that wants the vendor to maintain the application or needs features OrbitalWP does not provide.
Can OrbitalWP run on a private company network?
Yes. WordPress can run on a private server behind a company firewall and be limited to an intranet or approved VPN connections. The company is responsible for configuring and maintaining that environment.
Should I install OrbitalWP on my agency’s primary website?
You can, but a dedicated WordPress installation on a subdomain often provides a clearer separation between public marketing content and internal project work. Sensitive work may require a private server or intranet instead.
What should I test first?
Create a limited contractor account and assign it one representative task. Check what that user can see and change, then test your backup and restoration process.
Review the current OrbitalWP features and pricing to see whether it fits your workflow.