Requirements-led comparison · TaiGong 1.3.4

Looking for a GoPhish alternative?

01 / Fit assessment
Start with the outcome

A broader platform is not always the right answer.

If the requirement is an occasional, single-channel email exercise with basic campaign events, a lightweight deployment may be enough. TaiGong earns its place when follow-up and operating controls matter.

Keep the simpler workflow when

Email delivery is the whole job.

A basic tool may fit when one operator runs occasional exercises and risk analysis, training, automation, multiple delivery channels, and governed access live elsewhere.

  • Single-channel email
  • Occasional campaign cadence
  • Basic event review
  • No managed SaaS requirement
Evaluate TaiGong when

The campaign is only the first step.

TaiGong connects core email simulation to risk and evidence, then adds licensed channels, stages, analytics, awareness, automation, RBAC, and auditing where required.

  • Continuing simulation program
  • Risk-based follow-up
  • SaaS or private delivery
  • Reviewable enterprise operations
Review one real workflow
02 / Practical comparison
Requirements, not slogans

Compare the operating model your team needs.

This table describes a typical basic GoPhish-style deployment, not every possible customization or third-party extension. Validate the current upstream project and your own integrations before making a decision.

RequirementTypical basic GoPhish workflowTaiGong 1.3.4
Email campaignsCore use case.Core Targets, groups, templates, pages, SMTP, results, and IMAP report monitoring.
SMS and supported enterprise IMUsually requires external tooling or customization.Licensed SMS plus DingTalk, Feishu, and WeCom with provider configuration.
Multi-stage and event automationUsually custom or external.Licensed Stages, time/event rules, scheduled jobs, and execution history.
Human-risk workflowUsually assembled outside the campaign tool.Core Risk signals and evidence; Licensed advanced views and exports.
Awareness trainingUsually an external workflow.Licensed Courses, batches, assessments, completion views, and follow-up.
Governed accessDepends on custom deployment and surrounding controls.Core tenant-aware resources and API tokens; Licensed RBAC and audit console.
DeploymentSelf-hosted.Delivered Managed SaaS and self-hosted paths are available.
SlackDepends on external integration.Integration-only Incoming-webhook event notifications; no Slack exercise delivery.
Microsoft Teams deliveryNot evaluated here.Unsupported Not a TaiGong 1.3.4 simulation-delivery channel.
03 / What TaiGong adds
Evidence · Risk · Follow-up

Continue after the email is sent.

The product difference is the connected operating loop, not a claim that every feature is free or that GoPhish cannot be extended.

Current coreCORE

A complete email campaign baseline.

Build and run authorized email exercises with groups, templates, landing pages, SMTP profiles, results, reporting events, risk signals, tenant-aware resources, and API tokens.

Measured extensionLICENSED

Add only the workflow you need.

Enable channels, stages, analytics, awareness, automation, RBAC, auditing, AI assistance, or advanced controls through the corresponding license.

Deployment choiceSAAS / SELF-HOSTED

Choose the operating boundary.

Use managed SaaS when application maintenance should stay with Yofune_Labs, or self-host when infrastructure and evidence must remain customer-controlled.

No unsupported promiseV1.3.4

Do not buy for a channel that is not shipped.

Slack is notification-only. Microsoft Teams delivery and an autonomous AI Agent are not represented as delivered capabilities in the current version.

04 / Evaluation method
No automatic migration claim

Recreate one representative exercise.

TaiGong does not claim an automatic GoPhish migration path. Evaluate fit by rebuilding one authorized workflow with equivalent targets, templates, landing pages, and sending configuration, then compare setup, evidence, reporting, and follow-up.

Go beyond the campaign

Compare one workflow, honestly.

Bring the scenario, operating constraints, and follow-up requirements your team uses today.