Software development, QA and IT support are commonly done from the Philippines. For many US, Australian and UK buyers, an employer of record (EOR) or a vendor contract is the quickest start, and an own entity makes sense once the team is steady. The part that needs the most care is code ownership, because a developer’s work does not belong to you just because you paid for it.
Read the outsourcing hub for the overview of all three models. This guide covers what changes when the work is software.
Which software tasks can be done from the Philippines?
Most remote-friendly software work can be done from the Philippines:
- Feature work in your stack, including front end, back end and APIs
- QA, test automation and release testing
- DevOps support, monitoring and on-call rotations
- Internal IT help desk, device setup and account administration
Work that needs a person in your office or at a customer site stays with your local staff. That includes hardware installation and any on-premise server work that needs physical access.
The sources this guide relies on set no licence for writing or testing software. Regulated products are different. If you build medical, financial or payment software, the licensing rules come from your home country and your regulator. Get that answer before you assign the work offshore.
What are the three ways to set up a development team?
| Model | Who employs the developer | Speed to start | Fits when |
|---|---|---|---|
| Freelancer or contractor | The contractor’s own business | Fastest | Short, defined projects with deliverables you can check |
| BPO vendor | The vendor | Fast | You want a managed team and accept less direct control of staff |
| Employer of record (EOR) | The EOR, under a contract with you | Fast | You need full-time staff without a Philippine entity |
| Own Philippine entity | Your company | Slowest | You want direct control of staff, code and IP over several years |
Software work pushes buyers toward a model that gives them the code and direct control of access. A freelancer’s business owns the output unless the contract says otherwise. An EOR employee is employed by the EOR, not by you. For steady, full-time developers, an EOR or your own entity fits better than freelancing.
The EOR vs BPO guide compares who employs the team and who manages the work. The contractor vs employee guide explains how the difference is tested.
Who owns the code your Philippine team writes?
Computer programs are protected literary works under Section 172.1(n) of RA 8293, the Intellectual Property Code. Ownership depends on how the work was created.
Employees. Section 178.3 gives the employer the copyright in work created during employment when it results from the employee’s regularly assigned duties, “unless there is an agreement, express or implied, to the contrary.” If the EOR is the employer, the default points to the EOR. Your contract should assign the work to you in writing.
Contractors. Section 178.4 covers work commissioned by someone other than the author’s employer. The person who commissions the work owns the work itself, but “the copyright thereto shall remain with the creator, unless there is a written stipulation to the contrary.” A freelance developer keeps the copyright in the code by default. That is why a contractor’s code needs a written assignment in the services agreement, signed before work starts.
Pair the assignment with confidentiality terms that cover source code, customer data and system credentials.
What do the Data Privacy Act and buyer-country rules require?
The Philippine Data Privacy Act
RA 10173 applies to processing of personal information, including processing done in the Philippines. Section 6 extends it to certain acts outside the country, such as processing personal information about Philippine citizens or residents.
One exclusion matters for a foreign software company. Section 4(g) says the Act does not apply to personal information originally collected from residents of foreign jurisdictions under the laws of those jurisdictions, including their data privacy laws, and then processed in the Philippines. User data you collected abroad will often fall in that exclusion, and your own country’s privacy law then does the work. Data collected in the Philippines, such as records of your Philippine staff, stays covered. Ask a Philippine privacy lawyer which side each data set sits on, and contract for the safeguards below either way.
Section 21 is the rule that matters most for outsourcing. A personal information controller stays responsible for personal information it transfers to a third party for processing, “whether domestically or internationally.” Under Section 3(i), a vendor or EOR can act as a processor, but your company still carries the accountability.
For development teams, the practical risk is production data. Keep developers out of production personal data by default, give access by named role, log it, and remove it when someone leaves. The Data Privacy Act guide covers the registration and breach duties.
UK and Australian buyers
The Philippine Act is only one layer. If your product handles customers’ personal data, your home-country privacy law also applies.
UK. UK GDPR restricts transfers of personal data to a processor in a country without UK adequacy regulations. The ICO’s appropriate safeguards page lists the IDTA and the UK Addendum as the standard data protection clauses for this purpose. Check the ICO adequacy list before each new transfer, because the list changes.
Australia. APP 8.1 requires an entity to take reasonable steps, before it discloses personal information to an overseas recipient, to make sure the recipient does not breach the Australian Privacy Principles. Under section 16C, the Australian entity can remain accountable for the recipient’s breaches.
This guide cites the UK and Australian rules because those regulators publish the guidance. US buyers should check their state privacy laws and any sector rules that cover their customer data.
Contractor misclassification
Philippine labor law reads the arrangement, not the label. Article 106 of the Labor Code covers contracting out, which starts “whenever an employer enters into a contract with another person for the performance of the former’s work.” A full-time freelancer who works your hours, takes daily direction and uses your laptops and accounts can look like your employee, whatever the contract says. Read the independent contractor guide before you hire anyone full-time on a contractor basis.
What does it cost, and what drives the price?
Quotes differ by role, seniority and model, so compare them on the same terms. Ask every vendor to show the base rate, any night premium, and their fee on top of pay.
Four things drive the cost:
- Role and seniority. A senior back-end engineer costs more than a QA tester, and an architect costs more than both.
- Shift. Article 86 of the Labor Code says every employee “shall be paid a night shift differential of not less than ten percent (10%) of his regular wage” for each hour worked between 10 p.m. and 6 a.m. An on-call rotation that covers your evenings pays this premium for every hour in that window.
- Statutory benefits and contributions. These sit on top of base pay for employees. A quote that leaves them out is not a full cost.
- Vendor or EOR fee. A BPO or EOR fee is separate from the developer’s pay, so the total is not the same as the salary.
The hire a Filipino virtual assistant guide covers how the legal test changes the cost of a contractor relationship.
What do foreign software companies get wrong?
- Hiring a full-time developer as a freelancer. This route carries a misclassification risk. Decide the model by the work, not the price.
- Assuming the code is yours because you paid for it. Under Section 178.4, a commissioned developer keeps the copyright unless the contract says otherwise. Get the assignment signed first.
- Giving the whole team production access on day one. Start with staging data and grant production access only to named people with a reason.
- Leaving the night premium out of the budget. On-call coverage for US or Australian hours changes the cost of the role.
- Choosing an own entity too early. An entity makes sense once the team size and roles are known. Starting with an entity before that adds fixed costs and admin.
- Skipping the buyer-country check. If the code touches a customer’s personal data, the UK or Australian rules can apply even when your developers sit in Manila.
When should you move from outsourcing to your own Philippine entity?
Move to your own entity when the team is steady, you want to employ staff directly, and you want direct control of code and access through your own company. A Philippine company can also apply for PEZA or BOI incentives if it qualifies. Eligibility depends on PEZA’s and BOI’s own rules, which the PEZA incentives page explains.
If you want the payroll and compliance handled while you build the entity, the PEO services page covers that option.
What is the next step?
Before you ask for quotes, write down three things: the roles you need, whether any developer will touch production personal data, and who will own the code. Then pick the model. Use a contractor only for defined projects with deliverables. Use an EOR or a BPO for steady staff. Move to your own entity once the team is established.
If you are ready to set up your own software team in the Philippines, start with the software company registration page. Put the assignment clause and the data terms into the contract before the first start date.
Frequently asked questions
Who owns the code a Philippine developer writes for my company?
It depends on the arrangement. Under Section 178.3 of RA 8293, an employer owns work created in the course of employment when it comes from the employee's regular duties, unless the parties agree otherwise. A commissioned contractor keeps the copyright under Section 178.4 unless there is a written stipulation. Put the assignment in writing either way.
Does an employer of record own the code its employees write?
The EOR is the legal employer, so the default rule in Section 178.3 points to the EOR, not to you. Your contract with the EOR should assign the work to you in writing. Do not rely on the default.
Can I hire a freelance developer to work full-time on my product?
Be careful. Philippine labor law looks at the work done and the control exercised, not the label in the contract. A full-time developer who takes daily direction, keeps your hours and uses your tools can be treated as an employee. Check the contractor test before you sign.
Do I need a Philippine company to hire developers?
No. A contractor, a BPO vendor or an employer of record can employ the team. Own entities suit teams that are already steady and they want direct control of staff and code.
Does the Data Privacy Act apply to developers working on my product?
Not always. Section 4(g) excludes personal information originally collected from residents of foreign jurisdictions under their laws and then processed in the Philippines, so your foreign users' data may fall outside it while your own privacy law still applies. Where the Act applies, under Section 21, the company that hands personal information to a third party for processing stays responsible for it. Limit production data access and put processing terms in the contract.
Do UK or Australian privacy rules apply if my developers work on customer data?
They can. UK GDPR requires an approved safeguard, such as the IDTA or the UK Addendum, for restricted transfers to a processor in a country without UK adequacy regulations. Australia's APP 8 requires reasonable steps before an overseas disclosure, and the Australian entity can stay accountable for the recipient's breaches.
Official sources
Primary references this guide is checked against.
- LawPhil: Republic Act No. 8293, Intellectual Property Code of the Philippines
- LawPhil: Republic Act No. 10173, Data Privacy Act of 2012
- LawPhil: Presidential Decree No. 442, Labor Code of the Philippines
- ICO: Adequacy regulations (UK GDPR international transfers)
- ICO: Appropriate safeguards (UK GDPR international transfers)
- OAIC: APP Guidelines, Chapter 8 (APP 8, cross-border disclosure of personal information)
Related guides
Marketing Outsourcing Philippines: Legal Setup Guide
Outsource SEO, ads, social media, design and video to the Philippines. Compare contractor, BPO, EOR and entity models, plus copyright, email and review rules.
Data Annotation Outsourcing Philippines: Legal Setup Guide
Outsource labelling, RLHF rating and content moderation to the Philippines. Compare setup models and the Data Privacy Act, moderator wellbeing and IP rules.
Insurance Outsourcing Philippines: Legal Setup Guide
Outsource insurance and mortgage back office to the Philippines: which tasks stay onshore, the FTC, APRA and FCA vendor rules, and Data Privacy Act duties.
