Compare
PHPTRAVELS vs Voyant: a finished product or a framework to build on
Both let you hold the code and run it on your own servers. PHPTRAVELS is a finished travel booking product, licensed once with the source included. Voyant is an open-source travel commerce framework published under Apache-2.0, which your engineers assemble into a platform.
- Product vs framework
- Commercial vs Apache-2.0
- PHP and MySQL vs Node and Postgres
- What works on day one
The short version
Ownership does not separate them; product shape does
Pick PHPTRAVELS if you want a working booking engine, B2B agent portal, admin and named supplier integrations from the first install, on a PHP and MySQL server you control. Pick Voyant if you have engineers who would rather build on an open-source framework than configure a finished product, and a permissive public licence matters to you. Voyant's licence is more open than ours. Use these steps to compare the two like for like.
- List what must work on launch day: products, suppliers, gateways and agents
- Count the engineering hours you have to build and maintain the platform
- Decide whether you need to redistribute the code or only run and change it
- Run both through the same booking and agent-markup script
- Check which stack your team, or your hosting partner, already runs
- Needed on launch day
- Booking engine and agent portal
- Engineering capacity
- One in-house developer
- Server stack
- PHP and MySQL
- Licence need
- Run and modify, no redistribution
- Hosting
- Our own server
At a glance
Three ways to run a travel platform you control
Voyant details below come from Voyant's own site and its public GitHub repository, as we read them in September 2026. Check the current position with the vendor before you rely on it.
- PHPTRAVELSFinished PHP product · one-time licence from the Startup planOne-time licence
- Voyant open sourceApache-2.0 framework · Node on Postgres, container image–
- Voyant CloudOptional managed deployment · price not published
Product or framework
PHPTRAVELS arrives as a booking product you configure. Voyant describes itself as a travel commerce platform your team composes into its own stack.
Licence terms
Voyant is Apache-2.0, so you can fork and redistribute it. PHPTRAVELS is a commercial licence with the source included: you host and modify it, but redistribution terms differ.
Stack
PHPTRAVELS runs on PHP and MySQL. Voyant runs as a Node application on Postgres and ships as a container image. Pick the one your team can operate.
B2B agents
PHPTRAVELS ships sub-agents, per-agent markups and wallets. Voyant does not state its B2B agent tooling in the material we read, so check with the vendor.
Supplier coverage
PHPTRAVELS lists its live supplier integrations by name. Voyant does not publish a supplier list we could confirm; ask which suppliers are live today.
Real cost
A free licence still needs build time, hosting and upkeep. A PHPTRAVELS licence is once, plus your hosting. Compare total cost, not licence cost.
Demo script
Run both through the same demo
With a framework, part of this script may need building before it can run. That is the comparison: note what works out of the box on each side.
Search
Search a real route or tour you sell, with real dates, and note how long results take.
Book
Book end to end through a payment gateway and find the booking in the admin.
Agent markup
Create a sub-agent, give them a markup and confirm the price they see differs from yours.
Cancel
Cancel or amend the booking and follow what happens to the supplier and the refund.
Add a supplier
Connect a supplier API and see whether it is configuration or development work.
Change something
Change a label or currency format and see who has to do it, and how long it takes.
Integrations
Suppliers and gateways: connected or still to build
On a framework, every supplier you sell is either already connected or a development task. List yours and check each one on both sides.
Supplier APIs
PHPTRAVELS lists its live supplier integrations by name on the integrations page. Ask Voyant which of your suppliers are connected today.
Payment gateways
Check which gateways each option supports in your market, and who builds and maintains any that are missing.
Your own credentials
Supplier contracts are usually between you and the supplier, so they move with you whichever platform you run.
If you are switching
What to plan when you move platforms
Both options keep your data on infrastructure you can control, which makes a move easier. These steps still decide it.
Export first
Get bookings, customers, suppliers and payment settings in a readable format before you change anything.
Reissue credentials early
Supplier contracts usually move with you, but API credentials often need reissuing. It is the slowest step.
Run both in parallel
Keep the old platform taking bookings while the new one takes test traffic on a subdomain.
Keep your URLs
Redirect old booking and content URLs one to one so you keep the search rankings you earned.
Move payments last
Switch payment gateways after everything else is proven. It is the step with real money attached.
Plan the stack change
Moving between PHP and MySQL and Node and Postgres means new hosting, backups and skills. Budget for it.
Side by side
PHPTRAVELS vs Voyant on the criteria that decide it
Voyant cells reflect Voyant's own site and GitHub repository in September 2026. Where it does not publish something, we say so instead of guessing.
| Criteria | Voyant | PHPTRAVELS |
|---|---|---|
| Deployment | VoyantSelf-host the open-source version, or use Voyant Cloud | PHPTRAVELSSelf-hosted on your own server |
| Source code | VoyantApache-2.0 on GitHub | PHPTRAVELSIncluded under a commercial licence |
| Pricing model | VoyantOpen source free; Cloud price not published | PHPTRAVELSOne-time licence |
| B2B agents and B2C site | VoyantSells trips online; check B2B agent tools with the vendor | PHPTRAVELSB2B agent portal and B2C site in one installation |
| Suppliers and APIs | VoyantNot published; check with the vendor | PHPTRAVELSLive integrations listed by name on the integrations page |
| Customisation | VoyantFork it under Apache-2.0, no permission needed | PHPTRAVELSChange the code yourself or commission it |
Best fit
Who each option suits
Choose PHPTRAVELS
You want booking flows, B2B agent tools and named suppliers working on day one, with source code and a licence you buy once.
Choose Voyant
You have engineers who want to compose their own stack on an open-source framework, and a permissive licence is a requirement.
Still deciding
Read the self-hosted vs SaaS guide, then cost the build hours a framework needs against a licence fee.
Why PHPTRAVELS
What PHPTRAVELS gives you on day one
A finished product
Booking engine, admin and agent portal ready to configure, not to build.
Source code included
Read, audit and change every line under a commercial licence.
Your servers, your data
Runs on PHP and MySQL hosting you choose and control.
B2C and B2B together
Public booking site and agent portal with markups and wallets in one install.
FAQ
PHPTRAVELS vs Voyant: common questions
What buyers ask when an open-source framework and a finished product are both on the shortlist.
Talk to salesOnly if you want a finished product rather than a framework. Both can be self-hosted and both give you the code, so ownership does not separate them, and Voyant's Apache-2.0 licence is more open than ours. PHPTRAVELS is the better pick when you want booking flows, B2B agent tools and named supplier integrations working on day one.
Product shape. PHPTRAVELS is a finished PHP travel booking product, with booking engine, B2B agent portal, admin and named supplier and payment integrations, licensed commercially with the source included. Voyant is an open-source framework on Node and Postgres that your engineers compose into a platform.
Yes. Voyant publishes the platform under Apache-2.0 on GitHub, which lets you fork and redistribute it. PHPTRAVELS includes the source under a commercial licence, so you can host and modify it, but redistribution terms differ. If a permissive public licence is a hard requirement, that is a real reason to pick Voyant.
Voyant's open-source version has no licence fee, and Voyant Cloud pricing was not published when we checked. PHPTRAVELS is a one-time licence. Compare total cost over three years: build hours, hosting, upkeep and integrations, not only the licence.
Both need someone to run a server, so that cost is similar. The difference is what developers spend time on: with PHPTRAVELS the booking flows and supplier connections already exist and a developer extends them; with a framework, a developer typically builds them first.
Usually. Because both keep data on infrastructure you can control, exporting is simpler than leaving a rented platform. Map bookings, customers and supplier settings from Postgres to MySQL, reissue supplier credentials early and run both in parallel before switching.