Here's the honest answer up front: Amelia is built for salons, clinics, gyms, and one-on-one services like photographers or coaches — not for tour and activity operators. Tour operators can technically use it, but you'll be making the software do something it wasn't built for, and most of the work falls on you. Kong is built specifically for tour operators in Malaysia and Southeast Asia.
The real question isn't features — it's whether you want a booking system you have to set up and maintain yourself inside a WordPress website, or one that's ready to take bookings from day one. Amelia lives inside your WordPress site. If you don't have a WordPress site, you need to build one first. If you do have one, you (or your developer) maintain it — the hosting, the updates, the plugin compatibility, the security patches. Kong handles all of that for you, and most operators are taking bookings within a day of signing up.
I spent six years at Rezdy, Checkfront, and Regiondo before co-founding Kong. I'm not neutral about this comparison, but I'll be honest about where Amelia genuinely wins — anything less would be useless to you as a buyer.
For operators outside Malaysia: Kong serves operators globally. This comparison leans Malaysian where Kong's local payment options (Touch 'n Go, ShopeePay, FPX, etc.) matter most, but the bigger point — that Amelia is built for appointment businesses, not tour operations — applies everywhere.
TL;DR by operator type
Choose Amelia if
- You already run a WordPress site and have someone who maintains it
- Your business is more appointment-based than tour-based (one person per booking, fixed time slot)
- You run multiple types of services (appointments, classes, events) and want one tool for all of them
- You specifically prefer paying once and owning the license rather than using a monthly platform
- You have a developer to help with setup and ongoing fixes when things break
Choose Kong if
- You don't have a WordPress site (and don't want to build and maintain one)
- Your tours are group-based — multiple guests sharing seats on the same departure
- You want to start taking bookings within a day, not in a few weeks
- You take Malaysian payment methods (Touch 'n Go, FPX, ShopeePay, GrabPay, Boost, DuitNow QR)
- You'd rather pay nothing as an operator than buy a license plus pay for hosting and maintenance
- You want to list your tours on OTAs like GetYourGuide later
At a glance
| Feature | Amelia | Kong |
|---|---|---|
| What it is | A plugin you install inside a WordPress website | A booking platform you sign up for and start using |
| Where it lives | Inside your WordPress site (you maintain the site) | On Kong's servers (we maintain everything) |
| What you pay | Once for the license, then ongoing for hosting & maintenance | Nothing — free for operators |
| Lifetime license | Standard $299, Pro tier, Elite $799–$1,332 | Not applicable — no purchase |
| Annual subscription | Starter $49, Standard $89–$99, Elite $259–$432 | Not applicable — no subscription |
| Per-booking fee | None | 1.8% paid by guest on online direct bookings only |
| Walk-in / WhatsApp bookings | Manually entered, no fee | Free — no fee to operator or guest |
| Hosting & maintenance | You handle it (or pay someone) | We handle it (free, included) |
| Built for | Appointment businesses — salons, clinics, gyms, coaches | Tour and activity operators |
| Group bookings (multiple seats per tour) | Possible but requires setup work; not the default | Built in from the start — it's how tours work on Kong |
| Payment gateways | Stripe, PayPal, Mollie, Razorpay, WooCommerce, Square | Stripe OR Xendit (operator picks) |
| Touch 'n Go / ShopeePay / Boost / DuitNow QR | Not supported | Supported via Xendit |
| Digital waivers | Need to install separately and configure | Included free, ready to use |
| OTA connections (GetYourGuide, Klook, Viator) | Manual or developer-built | GetYourGuide live; more in development |
| Mobile app | None | Yes |
| Support | Email tickets and community forums | Founder-led WhatsApp in Malaysian business hours |
| Public operator rating | WordPress.org 4.6/5 (761), Capterra 4.9/5 (245), Trustpilot 3.6/5 (232) | Google Business Profile: 5/5 |
| Track record | Founded 2018; ownership changed from TMS to Suspended Networks | New (founded 2025) |
Pricing verified June 2026 from wpamelia.com/pricing/ via Booknetic's May 2026 Amelia review. USD/MYR exchange rate of approximately 4.06 used for ringgit conversions throughout.
Do you want to set up the booking system yourself, or have it ready to go?
This is the real decision behind Amelia vs Kong, and it's worth thinking about honestly because both options are legitimate — they fit different operators.
How Amelia works. Amelia is a plugin you install inside a WordPress website. If you already have a WordPress site, that means downloading the plugin, activating it, going through the setup wizard, configuring your services, your prices, your schedule, and your payment gateway. If you don't have a WordPress site, you need to build one first — that means buying hosting (around RM 40–200/month), buying a domain, choosing a theme, setting up SSL, and probably hiring someone to make it look professional.
Once Amelia is up and running, you (or whoever you hired) maintain it. WordPress releases updates every few months — when those happen, you need to test that Amelia still works with the new version. Sometimes plugins break after updates. Sometimes your theme stops working after updates. Sometimes you get a security warning and need to fix it before guests can book. None of this is dramatic, but it's ongoing work — the kind of work that's easy to forget about when you're evaluating Amelia's $299 lifetime license and thinking "this is cheap."
The honest case for Amelia: you genuinely want to own your booking system, and you have the technical capacity (or someone you trust) to maintain a WordPress site. If you're already doing this for your main business website, adding Amelia is a small extra step. The license is one payment, and you keep it.
How Kong works. You sign up at bookwithkong.com, fill in your business details (your tours, prices, schedule, capacity), and you're taking bookings. Most operators are live within a day. We handle the hosting, the security, the updates, the payment integration, the mobile experience, all of it. If something needs fixing, you message us on WhatsApp and we fix it. There's nothing for you to maintain.
The honest case for Kong: you want to spend your time running tours, not running a website. Most Malaysian tour operators we work with didn't get into this business to become amateur web developers. The hosted approach removes a whole category of work from your plate.
Which one fits depends on three honest questions:
- Do you already have a WordPress site? If yes, Amelia is a marginal addition. If no, choosing Amelia means committing to building and maintaining a website on top of choosing your booking system — that's a much bigger commitment than the license fee suggests.
- Do you have someone technical you can call when things break? WordPress sites occasionally break — themes conflict with plugins, updates introduce issues, the booking widget stops appearing after a change. If your answer is "my nephew set it up last year and I haven't talked to him since," that's the wrong answer to be giving when guests can't book a tour. Kong is one number you call when something needs help, regardless of what.
- Do you want to spend your time on tours or on the website? This is the question most operators don't ask themselves until they're a few months into running a WordPress-based booking system. The maintenance time is real, especially in the first six months.
For most Malaysian tour operators we talk to, the hosted approach fits better — not because WordPress is bad, but because "I run tours, I don't want to run a website" is a reasonable position. For operators who specifically want the control of owning their own site and have the capacity to maintain it, Amelia is a legitimate choice.
Amelia is built for one-on-one bookings, not group tours
This is the part most operators don't realise until they've already chosen Amelia. The pricing looks reasonable. The booking widget looks nice. Then you try to set up a tour and the software starts fighting you.
Amelia is designed around appointments. A customer picks a service (haircut), picks the staff member (Sarah), picks a date and time (Tuesday 2pm), and books that slot. That's the natural flow. It works perfectly for salons — Sarah is doing one haircut from 2pm to 3pm, the slot is taken, nobody else can book it. Same for clinics, gyms with personal trainers, photographers, coaches, consultants.
Tours don't work that way. Your 9am snorkel trip has 8 seats. A family of 4 books, then later a couple books, then a solo traveller books — and you've still got one seat left for someone else. Your guests aren't booking "Aiman the guide" — they're booking the 9am departure. Your guide isn't doing one snorkel trip per person; they're taking the whole group out together.
Amelia can handle this, but only if you configure it carefully. You have to turn on "group bookings," set minimum and maximum capacity correctly, enable "allow booking above minimum capacity," configure "keep slot available after first booking," and decide between "open group" and "closed group" logic. The documentation explains all of this, but you're essentially convincing the software to behave like a tour booking system instead of letting it do what it's naturally good at.
Real problems Amelia operators have reported when running tours:
- Setting up a tour is harder than it should be. You're navigating menus designed for "service" and "employee" rather than "tour" and "departure." Operators have to translate their actual business into Amelia's language before they can start.
- The employee concept doesn't fit tours. Amelia assumes each booking is tied to a specific staff member. Tours usually aren't. Operators end up creating fake "employees" just to make the software work, or accept that the booking flow shows information that doesn't apply to their tour.
- Cancellations don't always reopen the slot properly. Multiple operators have reported that when a guest cancels, the seat doesn't always become available again the way you'd expect. This is documented in Amelia's user feedback forum and is a known issue.
- No way to list on OTAs without a developer. Amelia doesn't connect to Klook, Viator, or GetYourGuide automatically. You'd need to either manage inventory manually across each OTA (error-prone, time-consuming) or hire a developer to build an integration. Kong's GetYourGuide connection is already built in.
The honest reality: tour operators on Amelia are using a tool designed for a different kind of business. It works, but you're always nudging it to behave the way you need it to. For appointment-style operations within tours — like a private fishing charter where one guide takes one party out — Amelia fits more naturally. For the typical Malaysian tour (group experiences, shared capacity, fixed departures), it's harder than it needs to be.
Pricing comparison
Amelia's pricing (current as of June 2026)
Annual subscription (per year, with monthly updates and support during subscription):
| Tier | Price | Domains | Best for |
|---|---|---|---|
| Lite (Free) | $0 | 1 domain | Very basic test setup, Square payments only |
| Starter | $49/yr | 1 domain | Single-product operations, no Stripe |
| Standard | $89–$99/yr | 1 domain | Most appointment-based businesses; full payment gateway support |
| Pro | (tier between Standard and Elite) | 1 domain | Advanced features for growing businesses |
| Elite | $259–$432/yr | Unlimited domains | Multi-location, developer API needs |
Lifetime license (one-time payment, lifetime updates and support):
| Tier | Price |
|---|---|
| Standard | $299–$332 |
| Elite | $799–$1,332 |
Source: wpamelia.com/pricing via Booknetic's May 2026 Amelia review.
Beyond the license, Amelia operators also pay for:
- WordPress hosting (typically $10–$50/month for a small business site)
- Domain name ($10–$15/year)
- WordPress theme (often $50–$80 one-time or $99/year for premium themes)
- SSL certificate (usually free via hosting provider)
- Developer time for setup, customization, integrations (variable — could be $500–$5,000 one-time)
- Payment gateway fees (Stripe, PayPal, etc. at the gateway's own rates)
- Optional add-ons for advanced features (custom integrations, SMS notifications, etc.)
Kong's pricing
| Channel | Operator fee | Booking fee |
|---|---|---|
| Online direct (Kong-hosted website, embedded widget) | Free | 1.8% paid by guest at checkout |
| OTA bookings (GetYourGuide today, more in development) | Free | Currently no Kong fee — see note below |
| Walk-ins, phone bookings, WhatsApp bookings | Free | Free — no fee to operator or guest |
| Digital waivers | Free | Included as built-in feature |
| Website builder | Free | Included as built-in feature |
| Hosting, security, updates | Free | Included as part of Kong |
No tiers, no monthly subscription, no setup fee, no contract, no booking caps.
On OTA bookings: Kong currently doesn't charge an additional booking fee on bookings that come through OTA integrations. Kong's leadership hasn't finalized a long-term OTA fee structure and may introduce one in future. For now, operators using Kong's OTA integrations pay the OTA's commission and nothing additional to Kong.
The 1.8% guest fee applies only to bookings that flow through Kong's online checkout. It does not apply to walk-ins, phone bookings, or anything handled outside Kong's online flow.
Worked scenarios at real operator volumes
What does Amelia actually cost an operator? More than the license fee suggests — there's the hosting, the setup work, and ongoing maintenance to factor in. These scenarios compare what an operator actually pays over two years across both options.
Scenario A: Small Malaysian operator, no existing website
A growing operator with no website yet, choosing between Kong and setting up a WordPress site with Amelia. Running RM 5,000/month in revenue (about 37 bookings/month, average value RM 135). This operator would need to build a WordPress site from scratch to use Amelia. The numbers below show what that actually costs:
| Cost component | Amelia (Standard lifetime license) | Kong |
|---|---|---|
| Software license (paid once) | $299 ≈ RM 1,214 | RM 0 |
| WordPress hosting (24 months) | ~$15/mo × 24 ≈ RM 1,463 | RM 0 (included) |
| Domain name (2 years) | ~$25 ≈ RM 102 | RM 0 (Kong subdomain) or your own |
| WordPress theme | ~$80 once ≈ RM 325 | RM 0 (included) |
| Setting up the site (web developer) | ~$1,500 once ≈ RM 6,090 | RM 0 (we help via WhatsApp) |
| Payment processing (Stripe vs Xendit) on ~888 bookings over 24 months | Stripe: ~RM 4,300 | Xendit blended: ~RM 1,200 |
| Kong's 1.8% guest fee (paid by your guests) over 24 months | N/A | ~RM 864 paid by guests |
| Your total cost over 24 months | ~RM 13,494 | ~RM 1,200 (in payment processing) |
The honest takeaway: for an operator without an existing website, choosing Amelia means building and maintaining a WordPress site — that's most of the cost, not the license. Kong skips all of that.
Scenario B: Mid-size operator with an existing WordPress site
An established operator who already runs a WordPress site for their business, doing RM 50,000/month in revenue with about 200 bookings/month. They already pay for hosting, domain, and theme — so adding Amelia is just the license plus configuration.
| Cost component | Amelia (Pro lifetime, est. $499) | Kong |
|---|---|---|
| Software license (paid once) | ~$499 ≈ RM 2,026 | RM 0 |
| Hosting | Already paying | RM 0 |
| Setting up Amelia (web developer) | ~$1,500 once ≈ RM 6,090 | RM 0 |
| Ongoing developer help when things break (over 24 months) | ~$200/mo × 24 ≈ RM 19,488 | RM 0 |
| Payment processing on ~4,800 transactions over 24 months | Stripe: ~RM 19,200 | Xendit blended: ~RM 6,600 |
| Kong's 1.8% guest fee over 24 months | N/A | ~RM 9,720 paid by guests |
| Your total cost over 24 months | ~RM 46,804 | ~RM 6,600 (in payment processing) |
The big assumption here is ongoing developer help — about RM 800/month. Some operators don't pay this (they've got someone in-house, or they just live with things breaking sometimes). If you take that out, Amelia's 24-month cost drops to about RM 27,316 — still substantially more than Kong's RM 6,600. The Stripe vs Xendit difference alone (RM 19,200 vs RM 6,600) is enough to cover Kong's guest fee multiple times over.
Scenario C: Larger operator, around 600 bookings/month
An operator doing RM 150,000/month, around 600 bookings monthly. At this volume, a WordPress-based booking system needs more attention — better hosting, faster pages, more reliable backups, more developer time when things go wrong.
| Cost component | Amelia (Elite lifetime, $1,332) | Kong |
|---|---|---|
| Software license (paid once) | $1,332 ≈ RM 5,409 | RM 0 |
| Managed WordPress hosting (higher tier needed) | ~$80/mo × 24 ≈ RM 7,802 | RM 0 |
| Developer maintenance (more critical at this scale) | ~$500/mo × 24 ≈ RM 48,720 | RM 0 |
| Payment processing on ~14,400 transactions over 24 months | Stripe: ~RM 57,600 | Xendit blended: ~RM 19,800 |
| Kong's 1.8% guest fee over 24 months | N/A | ~RM 25,920 paid by guests |
| Your total cost over 24 months | ~RM 119,531 | ~RM 19,800 (in payment processing) |
At this size, maintaining a WordPress-based booking system becomes a real ongoing cost. Operators running this much volume on Amelia usually need dedicated technical help. Kong handles the scale without that overhead.
The honest counter: some operations at this size genuinely benefit from running their own setup — particularly if they connect their booking system to other tools (their CRM, accounting, marketing systems). For those operators, the developer cost is doing real work.
Summary across the three scenarios
| Operator profile | Amelia cost over 24 months | Kong cost over 24 months | What your guests pay (Kong) |
|---|---|---|---|
| Scenario A (small, no website) | ~RM 13,494 | ~RM 1,200 | RM 864 over 24mo |
| Scenario B (mid, has website) | ~RM 46,804 | ~RM 6,600 | RM 9,720 over 24mo |
| Scenario C (large, 600 bookings/mo) | ~RM 119,531 | ~RM 19,800 | RM 25,920 over 24mo |
Amelia's "no booking fees" pitch is technically true, but the total cost — including hosting, setup, and ongoing maintenance — adds up to more than most operators expect. Kong handles all of that as part of the platform.
Where Amelia honestly wins
| Amelia's advantage | Why it matters | The honest detail |
|---|---|---|
| Lifetime license model with no ongoing platform fees | Some operators specifically prefer one-time purchases over subscriptions, even if total cost is higher | This is a real preference, particularly for operators with strong opinions about software ownership. The lifetime model means no platform vendor can raise your monthly bill — though you carry ongoing hosting and maintenance costs separately. |
| Excellent booking flow for one-on-one appointments | The booking widget (pick service → pick staff → pick date → pick time → details → payment) is genuinely polished. Reviews consistently rate the customer experience highly | If your customers book one-on-one services (a haircut with a specific stylist at 2pm), Amelia's flow is one of the best in the industry. Kong's flow is built for tour groups instead, which is a different problem. |
| Multi-vertical support in one plugin | Amelia supports appointments, classes, events, and packages in one installation — useful for businesses with multiple service types | Kong is purpose-built for tour and activity operations. Mixed-vertical businesses (e.g., a yoga studio that also runs occasional weekend retreats) might prefer Amelia's broader fit. |
| Strong Capterra and WordPress.org ratings | 4.9/5 on Capterra across 245 reviews; 4.6/5 on WordPress.org across 761 reviews — established user base with mostly positive feedback | Kong's Google Business Profile rating is 5/5 but on a smaller (and different) review base. Amelia's track record is more established. |
| Active development through v9 release | Despite ownership transition concerns, Amelia continues active development with consistent point releases | The v9 launch in December 2025 had documented bugs and ongoing bugfix cadence through early 2026, but the platform is actively maintained. Operators choosing Amelia today aren't picking an abandoned plugin. |
| Full control over branding and booking flow | The booking widget lives inside your WordPress site, on your domain, in your theme. No "powered by [vendor]" footer | For operators who weight brand control heavily, this is a real advantage. Kong's hosted booking pages can be branded extensively but still live on infrastructure operators don't own. |
| Multiple payment gateway support | Stripe, PayPal, Mollie, Razorpay, WooCommerce, Stripe Connect, Square — flexibility across markets | Kong supports Stripe and Xendit. For operators with specific gateway requirements outside Malaysian context, Amelia's broader gateway list might matter. |
Where Kong honestly wins
Structural advantages
| Kong's advantage | Why it matters | The honest detail |
|---|---|---|
| Built specifically for tour and activity operations | Group bookings (multiple seats per departure) work the way you'd expect from day one | Amelia is built for one-on-one appointments; you can set up tours but it takes configuration work. For a typical Malaysian tour ("8 seats on a 9am snorkel trip"), Kong handles this naturally. |
| No WordPress maintenance burden | Hosting, security, updates, plugin compatibility, theme integration are all handled by Kong | Amelia operators carry ongoing WordPress operational responsibilities. For most tour operators (who didn't sign up to maintain a WordPress site), this is real overhead. |
| Choice of payment gateway (Stripe or Xendit) | Operators pick Stripe OR Xendit when they sign up; Xendit is much cheaper for Malaysian payments and accepts more local methods | Amelia operators use Stripe (or PayPal, Mollie, etc.) but can't use Xendit. Malaysian guests on Amelia can't pay with Touch 'n Go, ShopeePay, Boost, or DuitNow QR. |
| Native channel manager and OTA integrations | GetYourGuide live today; Viator and additional OTAs in development | Amelia doesn't have a native channel manager. Operators wanting to distribute through OTAs need to manually update inventory across platforms or build developer-led integrations. |
| Free walk-in and WhatsApp bookings, no platform fee | Bookings the operator generates themselves cost nothing through Kong | Amelia doesn't charge per-booking fees either, but it doesn't naturally model walk-in workflows the way Kong does. Manual entry of walk-ins works but isn't designed for. |
| Founder-led support in SEA business hours | WhatsApp access to founders, response times in minutes during Malaysian business hours | Amelia's support is email/ticket-based with community forums. Different model — neither is inherently better, but the speed differs significantly for SEA operators with operational questions. |
| Independent platform | Single product, single team, single roadmap | Amelia transitioned ownership from TMS to Suspended Networks in recent years. The platform remains active but the strategic direction is set by the new owner. Operators making multi-year commitments are tied to that strategic direction. |
Experiential advantages
| Kong's advantage | Why it matters | The honest detail |
|---|---|---|
| Setup measured in hours, not days or weeks | Most Kong operators are live and taking bookings within a day of signing up | Amelia setup includes WordPress site setup (if needed), plugin configuration, payment gateway integration, theme integration, and testing. For operators starting from scratch, this is a multi-week project. For operators with existing WordPress technical capacity, it's faster but still meaningful work. |
| Mobile app for operators | Native mobile app for managing bookings, capacity, customers | Amelia's admin is web-based; operators access it through their mobile browser. Functional but not native-app polished. |
| No version compatibility concerns | Kong updates the platform centrally; operators don't manage version compatibility | WordPress plugin operators occasionally face "the plugin broke after WordPress 6.X update" issues. Amelia's v9 launch in late 2025 had documented bugs that affected operators. Kong's hosted model removes this category of risk. |
| Built specifically for Southeast Asian operators | Founder team based in Malaysia, product designed for local market dynamics | Amelia is built for global appointment-based businesses, primarily Western markets. Different ICP, different design assumptions. |
Payment processing — the Malaysian payment gateway problem
This is a deep cost and conversion difference between Amelia and Kong for Malaysian operators specifically.
Amelia operators must run payments through their chosen gateway — typically Stripe, PayPal, Mollie, Razorpay, or Square. For Malaysian operators, this almost always means Stripe (the most widely supported option in Amelia's gateway list with Malaysian merchant support). Stripe Malaysia charges 3% + RM 1 per transaction across all methods, and doesn't support Touch 'n Go, ShopeePay, Boost, DuitNow QR, or Malaysian BNPL.
Kong supports both Stripe AND Xendit. Operators choose which gateway to use when they sign up. Through Xendit, Kong accepts the full range of Malaysian payment methods that Amelia (via Stripe) can't process at all.
Payment method support comparison
| Payment method | Amelia (Stripe Malaysia) | Kong (with Xendit option) |
|---|---|---|
| FPX (online banking) | Yes — 3% + RM 1 | Yes — RM 1.20 flat per transaction |
| Local credit card | Yes — 3% + RM 1 | Yes — 2.00% |
| Local debit card | Yes — 3% + RM 1 | Yes — 1.20% |
| GrabPay | Yes — 3% + RM 1 | Yes — ~1.0%–1.7% |
| Touch 'n Go | Not supported | Yes |
| ShopeePay | Not supported | Yes |
| Boost | Not supported | Yes |
| DuitNow QR | Not supported | Yes |
| Malaysian BNPL | Not supported | Yes |
| International cards | Yes — 3% + RM 1 + 1.5% surcharge | Yes (varies by method) |
Source: Xendit Malaysia pricing, Stripe Malaysia published rates, Amelia gateway documentation.
The conversion implication: A Malaysian guest landing on an Amelia checkout page who wants to pay with Touch 'n Go (the largest e-wallet in Malaysia) cannot complete the booking. They either fall back to card payment (which they may not have set up for online use), abandon the booking, or look for an alternative provider that accepts their preferred payment method. This isn't a cost concern — it's a "did the booking happen at all" concern.
For Malaysian tour operators with meaningful local guest volume, the payment method support gap is more significant than the fee difference.
The ownership transition question
Amelia has gone through ownership changes. The original developer (TMS) transitioned ownership to Suspended Networks. The platform remains actively developed — version 9 shipped in December 2025 with consistent bugfix releases through early 2026 — but operators evaluating Amelia for multi-year commitments should know about the ownership trail.
The honest read: this isn't a strategic concern at the level of Bokun's Tripadvisor ownership (which creates direct supply-chain conflict) or FareHarbor's Booking Holdings ownership (which sets pricing through public-company dynamics). Amelia's ownership transition affects roadmap confidence and long-term direction more than it affects day-to-day operator economics.
For operators choosing a booking system today, the practical implications are:
- The plugin is actively maintained — v9 development through 2026, regular point releases, support remains responsive based on user feedback.
- Long-term roadmap is set by the new owner — operators have no visibility into Suspended Networks' multi-year plans for the platform.
- Capterra and WordPress.org ratings remain strong — 4.9/5 and 4.6/5 respectively, indicating user satisfaction hasn't materially degraded post-transition.
Kong is independent and operator-funded. The strategic direction is set by Kong's founders, not a parent company's quarterly earnings pressure or a new owner's portfolio strategy. Operators making multi-year commitments to Kong are committing to a platform whose roadmap they can directly influence through founder access.
The honest decision tree
| Your situation | Choose | Why |
|---|---|---|
| You already run WordPress and want booking inside it | Amelia | You're already maintaining WordPress, so adding the plugin is a small extra step |
| You don't have a WordPress site and don't want to build one | Kong | Amelia requires a WordPress site; choosing it means committing to building and maintaining one |
| Your bookings are one-on-one (one customer per slot) | Amelia | This is what Amelia was designed for |
| Your tours have shared seats (multiple guests per departure) | Kong | This is what Kong was designed for; Amelia works against this kind of setup |
| You have a developer you can call when things break | Either | Both work; the maintenance side of Amelia is manageable with technical help |
| You don't want to deal with WordPress when something breaks | Kong | We handle everything for you; one number to call when you need help |
| You need OTA connections (Klook, Viator, GetYourGuide) | Kong | GetYourGuide is built in; more in development. Amelia needs a developer to set this up |
| You take Malaysian payments (Touch 'n Go, FPX, ShopeePay) | Kong | Amelia can't accept these payments; Kong does via Xendit |
| You specifically want to own your website and booking system | Amelia | A legitimate preference; Amelia lives entirely inside your WordPress site |
| You want to be taking bookings within a day | Kong | Kong setup is hours; Amelia setup involves building/configuring a WordPress site first |
| You run different kinds of services (appointments + tours + classes) | Amelia | Amelia's one tool covers multiple types of services |
Frequently asked questions
Is Amelia a good fit for tour operators?
Amelia is built for appointment-based businesses — salons, clinics, gyms, coaches, photographers — where each booking is one customer at a specific time with a specific person. Tour operators can use Amelia, but you'll be setting it up to do something it wasn't really designed for. Group bookings (multiple seats per departure) work, but they require careful configuration. The software keeps asking you to assign "employees" to bookings, which doesn't fit how tours actually work. For most tour operators in Malaysia, a platform built specifically for tours (like Kong) is a more natural fit.
How much does Amelia cost in 2026?
Amelia's pricing has two models. Annual subscription: Starter $49/yr, Standard $89–$99/yr, Pro tier, Elite $259–$432/yr. Lifetime license: Standard $299–$332, Elite $799–$1,332. There's a free Lite tier with limited features (1 domain, 1 employee, Square payments only). Beyond the license, operators also pay for WordPress hosting ($10–$50/month), domain, theme, developer setup, and ongoing maintenance. Pricing is verified from wpamelia.com/pricing via Booknetic's May 2026 review.
Is Kong cheaper than Amelia?
Yes — once you add up everything you actually pay. Kong has no license fee, no hosting cost, no setup cost, and no maintenance burden. Amelia's "no booking fees" pitch is real, but you still need WordPress hosting, theme, setup, and usually some ongoing developer help. Across the three scenarios in this article, over 24 months Kong cost between RM 1,200 and RM 19,800 in payment processing; Amelia cost between RM 13,494 and RM 119,531 once hosting and developer time were included. The exception is operators who already maintain a WordPress site with in-house technical help — for them, Amelia's added cost is closer to Kong's.
Does Amelia support Touch 'n Go, ShopeePay, or Boost?
No. Amelia integrates with Stripe, PayPal, Mollie, Razorpay, WooCommerce, and Square — but none of these support Touch 'n Go, ShopeePay, Boost, DuitNow QR, or Malaysian BNPL in their Malaysian configurations. Kong's Xendit option accepts all of these Malaysian payment methods.
Does Amelia have a channel manager for OTAs?
Not natively. Amelia doesn't include a built-in channel manager for Klook, Viator, GetYourGuide, or other OTAs. Operators wanting to distribute through OTAs need to either manually update inventory across platforms or build a developer-led integration. Kong's GetYourGuide integration is native and live; Viator and additional OTAs are in development.
Is Amelia still actively developed after the ownership change?
Yes. Amelia's ownership transitioned from TMS to Suspended Networks, but the platform remains actively maintained. Version 9 shipped in December 2025 with consistent point releases through early 2026. Capterra rating remains 4.9/5 across 245 reviews; WordPress.org rating is 4.6/5 across 761 reviews. The ownership transition affects roadmap confidence more than day-to-day operator experience.
Can I use Kong if I'm not based in Malaysia?
Yes. Kong serves tour and activity operators globally — our current focus is Malaysia, but operators across Southeast Asia and beyond are on the platform. The free operator pricing, hosted setup (no WordPress to maintain), digital waivers, website builder, no booking caps, and OTA connections all apply regardless of where you're based. This comparison leans Malaysian in some places (the payment methods, the Xendit math), but the bigger argument — Amelia is built for appointment businesses, Kong is built for tours — applies everywhere. Outside Malaysia, the payment processing savings shrink, but the "I don't have to maintain a WordPress site" advantage still holds.
Can I switch from Amelia to Kong?
Yes, operators do switch between platforms. The main switching consideration is your WordPress site itself — if you've built your operator presence around a WordPress site that integrates Amelia, you'll need to decide whether to keep the site (and just remove Amelia, replacing with Kong's embeddable widget) or migrate to Kong's hosted booking page entirely. Bookings already on Amelia complete their lifecycle there; new bookings flow through Kong from the switch date. Product data, customer details, and pricing can typically be exported from Amelia and imported to Kong. Contact Kong's team via WhatsApp at +60 12-429 8159 to walk through the specifics.