Paca

June 17, 2026

Public disclaimer: This is an independent public teardown based solely on publicly available information retrieved on 2026-06-17. It is research support, not investment, legal, tax, or financial advice. Company-provided statements are labeled as claims, not verified facts. Paca did not participate in or review this report. Errors and omissions are possible; final decisions remain with the reader.

Out of what looks like a one-person project came an open-source rival to Jira, one where AI agents take seats on the Scrum board — and it climbed to 171 points on Hacker News on launch day. The code backs the story: an Apache-2.0 repository, releases landing almost daily, the kind of output that usually takes a team. Everything a venture outcome needs, though, sits outside that repository, and none of it is on the public record yet. We pulled 57 public sources into a five-partner, same-day read: cited, never spun. The whole case turns on whether a beloved free tool can grow into a business that captures what it creates. The teardown carries that answer. Read it before the founder call sets the terms.

What The Company Does

Paca describes itself as a self-hosted, Apache-2.0, "free forever" project-management system where AI agents work as Scrum teammates on a shared board rather than as a chatbot beside an existing tool (Paca homepage; Paca GitHub repository) company claim. The public product surface includes a Scrumban board, in-app AI chat, activity diff and revert, a built-in Model Context Protocol server, and a WebAssembly plugin system with a marketplace (Paca GitHub repository; Paca plugin overview; Paca MCP setup guide) company claim.

The buyer is not yet proven. The likely user is a small technical team that wants self-hosted human-plus-agent work management; the eventual payer would need to be a founder, engineering lead, product leader, product management office, or information-technology buyer. Paca has no public pricing page, says it is free, and lists hosted cloud only as an exploratory roadmap item (Paca homepage; Paca roadmap) company claim. That makes the current business model unknown, not merely early.

The product is real enough to merit attention, but the company is not yet proven as a venture. Public evidence supports launch-week open-source interest, technical build velocity, and a plausible wedge; it does not yet support independent production deployments, paid customers, a commercial owner, or a value-capture mechanism.

Key Takeaways

Investor reaction
Paca looks like a serious solo-builder artifact in a category that can produce very large outcomes, but the public evidence still reads as "impressive repository, not yet a company."
Current verdict
hold with medium confidence. The hold is pass-leaning and should be resolved through one cheap, time-boxed founder call rather than extended open-ended tracking.
Why investors might lean in
Hải Huỳnh appears to be a high-velocity builder, with a pre-1.0 product, roughly 967 to 988 GitHub stars, a 171-point Hacker News launch, and near-daily v0.4.x releases (Paca GitHub repository; Paca GitHub releases; Hacker News) source-backed fact.
Why investors might pull back
The core is Apache-2.0 and marketed as free, no paid product is published, independent deployment proof is absent from the public record, and the team footprint is one employee on LinkedIn (Paca license; Paca homepage; Paca LinkedIn company page) source-backed fact / company claim.
Highest-leverage fix
Publish or bring to the call one dated value-capture plan, with the free-versus-paid boundary defined, plus one independent production deployment reference or usage telemetry.
Best next move
Take one criteria-gated founder call. Move toward pursue only if value capture and independent demand both appear; move to pass if the answer is narrative, free-forever-only intent, or no deployment proof.

What Makes This Potentially Fundable

The fundable version of Paca is not "an open-source Jira clone with AI." The fundable version is a self-hostable control plane for teams where human workers and AI agents share tasks, permissions, project context, and auditability. If agentic workflows become a default operating mode, a system of record that natively manages agent work could become more valuable than a feature layered onto a legacy issue tracker.

The category can support venture-scale outcomes. Atlassian, Asana, monday.com, and GitLab collectively show billions in annual software revenue and high gross-margin work-management or adjacent developer-tool businesses (Atlassian annual report; Asana annual report; monday.com annual report; GitLab annual report) source-backed fact. GitLab and OpenProject also show that open-source software can attach paid enterprise or managed offerings (GitLab annual report; OpenProject pricing) source-backed fact / company claim.

What keeps the report honest is that Paca has not attached that engine. A large market, open-source precedent, and a strong builder do not create a fund-returning company unless the founder chooses and staffs a controlled capture layer.

The Four Holes To Close Before Fundraising

Hole	Investor Fear	What To Bring
No value-capture mechanism is visible.	A free Apache-2.0 product can create value that users, forkers, or incumbents capture instead of Paca.	A one-page commercial plan with a dated hosted, enterprise, support, marketplace, or usage-based product and a named owner.
No independent deployment proof is public.	GitHub stars and Hacker News points may be launch attention rather than production usage.	Install telemetry, Docker pull data, named production references, support tickets, or paid pilots.
Team coverage is engineering-heavy and business-light.	One founder may ship the product but lack the capacity to sell, secure, support, and finance an enterprise-grade tool.	Org chart, committed contributors, hiring plan, commercial owner, security owner, and fundraising intent.
The wedge overlaps powerful alternatives.	Atlassian Rovo, Linear agents, Multica, Agiflow, Plane, and other alternatives may neutralize the agent-workflow story before Paca builds distribution.	A head-to-head proof point showing a buyer who needs self-hosted, agent-controlled project management that incumbents will not serve.

Decision Snapshot

One-sentence company description: Paca is an early, self-hosted, AI-native project-management tool that claims to put human teammates and AI agents on the same Scrum board.
Screen: hold, pass-leaning.
Confidence: medium.
Suggested next action: One criteria-gated founder call, pre-committed to pursue or pass triggers.
Why this matters now: The product has launch attention and a fast builder, but the decisive unknowns are founder-only answers that public research cannot resolve.
Investor-readiness diagnosis: Paca is technically interesting but not fundraising-ready because value capture, independent demand, commercial ownership, and enterprise-readiness remain unproven.
Best founder use of this report: Prepare the proof packet investors will ask for first: commercial plan, deployment proof, team plan, security posture, and incumbent-differentiation evidence.

IC Disagreement Map

The partners reviewed the same evidence dossier independently: the power-law lens tests fund-returning upside, the prepared-mind lens tests timing and category structure, the founder-jockey lens tests team capability, the risk-reduction lens tests fatal flaws, and the long-horizon lens tests compounding and ownership logic.

Power-law partner
holdmedium confidence
Paca could become a fund-returning platform if an open-core or managed-cloud layer attaches to the agent-native control plane, but the capture layer is not evidenced today.
Would flip on
A dated monetization intent plus independent deployment proof would move this partner toward pursue; a confirmed free-forever-only path with no raise would move this partner to pass.
Prepared-mind partner
holdmedium confidence
Category timing is attractive and the self-hosted Model Context Protocol wedge is specific, but incumbents and funded peers can absorb much of the visible differentiation.
Would flip on
Deployments chosen specifically for self-hosted agent control plus a named monetization path would move this partner toward pursue; incumbent or peer parity with no Paca demand would move this partner to pass.
Founder-jockey partner
holdmedium confidence
The founder's technical execution is the strongest verified signal, but public evidence does not cover commercialization, hiring, enterprise security, or demand creation.
Would flip on
A real team or active recruiting plus a commercialization plan would move this partner toward pursue; confirmed sole-maintainer status with no monetization or hiring intent would move this partner to pass.
Risk-reduction partner
holdmedium confidence
The product and builder are real, but the intersection of permissive license, free positioning, solo footprint, and no public capital is close to a structural no.
Would flip on
A dated commercial plan, an independent paying or hosted reference, and a team to sell would move this partner toward pursue; an explicit no-monetization commitment or stacked kill criteria would move this partner to pass.
Long-horizon partner
holdmedium confidence
A reversible monetization gap on top of a high-velocity builder is worth tracking cheaply, but there is no entry vehicle, cap-table context, or compounding asset yet.
Would flip on
A stated capture layer on a dated roadmap plus a second hire or financing would move this partner toward pursue; an explicit free-forever-only commitment with no commercial intent would move this partner to pass.

No partner changed vote or confidence after the evidence-request round; all five confirmed hold / medium. The identical vote and confidence were treated as an alarm rather than comfort: the agreement is evidential because five lenses converged on the same missing proof, while the direction of lean remains meaningfully different.

Scenario Range

Scenario	What The Company Looks Like In 3-5 Years	Falsifiable Trigger To Watch	Earliest Evidence
Strikeout	Paca becomes a respected but maintenance-mode open-source repository with no paid product, no staffed company, and no durable distribution before incumbents absorb the agent-board feature.	Stars or forks rise while deployments, hiring, and monetization remain absent at the next checkpoint.	The current public record already shows launch attention, one-employee company footprint, no published paid product, and no independent deployment proof.
Base	Paca becomes a useful open-source project with a modest hosted, support, or enterprise business for a niche of self-hosted technical teams.	A defined open-core boundary and the first referenceable paying or hosted users appear, but the buyer pool stays niche and the team remains small.	A hosted or enterprise SKU, a paid pilot, and one or two referenceable teams within 12 to 18 months.
Home run	Paca becomes the default self-hosted control plane for human-plus-agent software teams, with a managed or enterprise layer, retained customers, and a growing plugin or integration ecosystem.	Independent migrations cite self-hosted agent control as the reason, paid retained logos appear, and third-party plugin or contributor activity compounds.	One named production deployment, a paid SKU, shipped enterprise controls, and sustained non-bot contributor growth.

What Investors Will Test

What We Looked For	Current Read	Investor Implication	Founder Prep Priority
Home-run mechanism	The category is large, but Paca's revenue mechanism is `unknown`.	Investors will not underwrite category size without a controlled way to capture value.	Bring a dated commercial plan and free-versus-paid boundary.
Outside validation	Public evidence shows GitHub and Hacker News attention, not production deployment.	Investors will treat launch interest as a proxy, not traction.	Bring deployment telemetry or a referenceable user.
Category timing	AI in work management is timely, but incumbents are already shipping agents and Model Context Protocol integrations.	The wedge must be structural, not merely a feature race.	Explain the buyer requirement incumbents will not serve.
Founder capability	Technical build capability is `evidenced`; go-to-market and fundraising coverage are `absent` in the public record.	The founder-call bar is company-builder readiness, not demo quality.	Bring team, hiring, ownership, and commercial ownership evidence.
Incentive alignment	Apache-2.0 and free positioning maximize adoption but threaten value capture.	Investors will ask who pays and what Paca controls.	Define the stakeholder that pays and the asset Paca owns.

Claim Reconciliation: Inconsistencies Investors Will Catch

Claim Or Metric	Where It Appears	Conflicting / Unreconciled Versions	Why Investors Flag It	How To Reconcile
Team size and dogfooding	Hacker News Paca LinkedIn company page	The founder says "my team uses it daily," while LinkedIn shows one employee and the repository appears founder-dominant.	Investors will not know whether this is team usage, founder usage, or informal contributor usage.	Bring a named org chart, full-time status, ownership areas, and active internal usage evidence.
GitHub traction count	Paca GitHub repository Paca GitHub releases	The same-day snapshots show roughly 967 to 988 stars and 55 to 57 forks.	The drift is not material, but it reminds investors that platform metrics are snapshots rather than operating metrics.	Report a dated snapshot and stop using stars as a deployment proxy.
Latest product version	Paca GitHub repository Paca GitHub releases	Repository and release pages showed slightly different v0.4.x states on the same retrieval date.	Investors will view this as normal release timing, but it confirms the product is pre-1.0 and moving quickly.	Use the releases page as the canonical release record and state the product is pre-1.0.
Funding status	Paca homepage Paca GitHub repository	No disclosed funding is visible publicly; private SAFE, angel, or note rounds may still exist.	Ownership and runway cannot be inferred from the public record alone.	Bring cap table, SAFE or note summary, runway, and fundraising intent.
AI differentiation	Paca GitHub repository Atlassian Jira AI Atlassian Rovo Linear Multica Agiflow	Paca claims agents as teammates, while incumbents and peers also claim agentic work-management capabilities.	Investors will not accept "AI-native" as differentiation without a buyer reason incumbents cannot copy.	Bring a feature, security, deployment, and buyer-requirement matrix.

Diligence Findings: Issues To Fix Before You Raise

1 deal-breaker3 high2 medium

No company-controlled value-capture mechanism is visible on a free Apache-2.0 core.
deal-breaker if confirmed as permanent.
Commercial diligence.
Fix
Define a paid layer, price logic, owner, and timeline.
No independent production deployment or paid customer proof is public.
high
Customer and traction diligence.
Fix
Provide telemetry or named references that can be checked.
The founder appears to carry nearly all public product-building evidence.
high
Team diligence.
Fix
Name committed team members, hiring plan, and areas of ownership.
Incumbent and peer overlap is already visible.
high
Market and product diligence.
Fix
Show buyer-specific reasons Paca wins against Jira, Linear, Plane, Multica, and Agiflow.
Enterprise access controls and compliance artifacts are not yet public.
medium
Technical and security diligence.
Fix
Ship or date role-based access, single sign-on, audit logs, scoping, and buyer-facing security docs.
WebAssembly plugin and Model Context Protocol security claims lack independent validation.
medium
Technical diligence.
Fix
Produce an external audit, threat model, signed artifacts, and guardrail plan.

Data Room Readiness Checklist

Procurement-readiness score: not ready
Rationale: Paca is self-hosted and early, but the likely paying buyers would still require access controls, security documentation, signed artifacts, support commitments, and a clear responsibility model before they treat it as enterprise software.

Data Room Area	What Investors Expect	Current Read	Status	Priority
Company overview & corporate	One-pager, incorporation, good standing, structure	Brand and product are public; corporate entity details are not public.	`missing`	High
Financials	Monthly profit and loss, three-year model with assumptions, burn and runway	No revenue, burn, or runway data is public.	`missing`	High
Cap table & funding history	Clean cap table, prior rounds, SAFEs or notes, 409A	No disclosed funding is public; private instruments may still exist.	`missing`	High
Legal & IP	Bylaws, board consents, IP assignments, material contracts	Apache-2.0 license is public; assignments and contributor rights are not public.	`partial`	High
Product & technology	Roadmap, architecture overview, security and compliance docs	Architecture, roadmap, deploy docs, security policy, and plugin docs are public; controls and audits are incomplete.	`partial`	High
Team	Org chart, key employment or advisor agreements, vesting	Founder identity is public; team beyond founder is unconfirmed.	`missing`	High
Customers & traction	Retention cohorts, revenue bridge, pipeline, references	Stars and Hacker News points are public; customers and deployments are unknown.	`missing`	Critical
Market & competition	Market sizing, competitive landscape, pricing	Public comps and competitor pages support a first-pass map; Paca pricing is missing.	`partial`	Medium

First-Call Agenda For The Startup

Time	Topic	Founder Goal	Evidence To Bring
0-10 minutes	Company intent	Separate venture company intent from open-source project intent.	Clear answer on raising, ownership, and whether Paca is intended to become a business.
10-25 minutes	Value capture	Show the paid product and what Paca controls.	Dated hosted, enterprise, support, marketplace, or usage-based plan with free-versus-paid boundary.
25-40 minutes	Demand proof	Prove real teams run Paca outside the founder's own environment.	Telemetry, Docker pulls, references, active projects, or support tickets.
40-50 minutes	Team and execution	Show who will build, sell, secure, and support the product.	Org chart, committed contributors, hiring plan, commercial owner, and security owner.
50-60 minutes	Defensibility and risks	Explain why Paca wins against incumbents and how security risks are controlled.	Head-to-head matrix, buyer requirement, security plan, and supply-chain controls.

Business Model And Revenue Signals

Paca is marketed as free and open source.
Company-controlled page.high
SourcePaca homepage Paca GitHub repository
This is adoption-friendly and value-capture-negative unless paired with a paid layer.
Hosted cloud is listed as exploratory.
Roadmap.medium
SourcePaca roadmap
This keeps the option open but does not evidence intent.
OpenProject shows self-hosted project-management buyers can pay.
Pricing page.medium
SourceOpenProject pricing
This is a precedent, not Paca traction.
GitLab shows open-core can scale in adjacent developer workflows.
source-backed factPublic-company filing.high
SourceGitLab annual report
The analogy depends on Paca defining its own paid boundary.

Google Search and the Paca website were checked and showed no public pricing page or paid product SKU. These absences carry little weight since early-stage companies often keep pricing private until launch.

Public revenue, profit, annual recurring revenue, gross margin, customer concentration, and paid retention are not available for Paca. Any revenue scenario would be speculative until the founder provides a monetization plan and deployment denominator.

Revenue Quality Checklist

Before Paca can move from hold to pursue, the founder should be prepared to show raw evidence for annual recurring revenue or paid-pilot revenue if it exists, active deployments, conversion from open-source users to paid buyers, customer concentration, gross revenue retention, net revenue retention, churn, customer acquisition cost, lifetime value, payback period, and support burden. These figures must tie across the deck, model, bank or billing exports, invoices, deployment telemetry, and customer references.

Funding And Ownership Context

Item	Public Read	Evidence Label	Diligence Request
Total raised / rounds	Not public.	`unknown`	Provide all SAFEs, notes, equity rounds, grants, angels, and amounts.
Instruments (equity / SAFE / notes)	Not public.	`unknown`	Provide instrument list, caps, discounts, and outstanding obligations.
Investors	Not public.	`unknown`	Provide investor and advisor list, if any.
Post-money valuation	Not public.	`unknown`	Provide last priced valuation or proposed financing terms.
Cap table / ownership	Not public.	`unknown`	Provide founder ownership, option pool, contributor or advisor equity, and any entity structure.
Burn & runway	Not public.	`unknown`	Provide monthly burn, personal runway, infrastructure spend, and large-language-model cost exposure.
Next-round plan	Not public.	`unknown`	State whether Paca intends to raise and what milestones the round finances.

Crunchbase and Google Search were checked and showed no matching company profile or disclosed funding round. These absences carry little weight since SAFE, angel, and private rounds often stay undisclosed.

Founder And Team

Hải Huỳnh
Public founder and primary builder associated with Paca.
Hải Huỳnh GitHub Hải Huỳnh LinkedIn Hacker News
Evidencesource-backed fact
Confidencehigh
pikann commit footprint
Public repository shows founder-dominant product build activity.
Paca GitHub repository
Evidencesource-backed fact
Confidencehigh
Paca company footprint
LinkedIn company page shows one employee and a build-in-public launch post.
Paca LinkedIn company page
Evidencesource-backed fact / company claim
Confidencemedium
Founder launch narrative
The founder states that the team uses Paca daily and that the project was built from passion.
Hacker News
Confidencemedium

Founder Competency Coverage

Competency	Hải Huỳnh	What The Evidence Is
Domain depth	`evidenced`	Paca's product, public launch discussion, and technical posts show role-relevant product and workflow thinking.
Technical build capability	`evidenced`	Public GitHub evidence shows a multi-service product, active releases, and founder-dominant commits.
Product	`evidenced`	Paca has a coherent public product surface, roadmap, and launch positioning.
GTM / sales	`absent`	No public sales, partnerships, paid customers, or commercial owner evidence is visible.
Leadership / hiring	`claimed`	The founder references "my team," but the public company footprint shows one employee and no public hiring.
Fundraising history	`absent`	No disclosed raise or startup database profile is visible publicly.
Prior founding outcomes	`claimed`	Prior GitHub repos exist, but independent outcomes are unverified.

Multi-service AI-agent project-management platform
Medium
Team coverage today
Covered technically by the founder's public build record.
What would close it
Show maintainers beyond the founder and production reliability evidence.
Commercial open-core or hosted model
Critical
Team coverage today
Not covered in public evidence.
What would close it
Name the paid boundary, owner, and first buyer evidence.
Enterprise security and compliance readiness
High
Team coverage today
Partially covered by docs and roadmap, not by shipped controls or audits.
What would close it
Ship or date controls and obtain independent security validation.
Team scaling and fundraising
High
Team coverage today
Not covered in public evidence.
What would close it
Provide org chart, recruiting plan, cap table, and financing intent.

Public Professional Footprint

These checks carry low decision weight by design: they corroborate the competency table and sharpen founder-call questions; none of them alone changes the verdict.

Signal	Hải Huỳnh	What The Public Record Shows
Technical artifacts (repo level)	`evidenced`	Public GitHub shows Paca plus earlier Go, TypeScript, Python, and machine-learning repositories; one noted fork does not drive the build read.
Professional social content	`evidenced`	Hacker News and LinkedIn activity focus on Paca architecture, launch, plugins, and workflow claims; traction claims from those posts remain company-originated.
Education / credentials	`claimed`	LinkedIn lists Danang University of Science and Technology.

Google Search and public patent databases were checked and showed no independent education verification or attributable publications or patents. These absences carry little weight for early-stage founders.

Net read: the footprint strengthens the technical-builder case and does not close the commercial, team, or value-capture gates.

Founder-Market Fit Read

What is promising: The founder appears to have the technical taste and shipping velocity to build the hard product surface for agent-native project management.
What is missing: The public record does not show enterprise sales, monetization, hiring, fundraising, security leadership, or independent customer creation.
What to prepare: Bring the company-builder proof, not another demo: monetization plan, reference deployment, team plan, and a security roadmap.

mammam-related repositories
Prior founder-associated public GitHub project family.
Hải Huỳnh GitHub repositories
Evidencecompany claim / inference
Confidencelow
Follow-upAsk what shipped, who used it, and why it ended.
toptimviec-backend
Prior founder-associated public GitHub repository.
Hải Huỳnh GitHub repositories
Evidencecompany claim / inference
Confidencelow
Follow-upAsk for users, outcomes, and lessons.
Paca AI LinkedIn company page
Current company surface.
Paca LinkedIn company page
Evidencesource-backed fact / company claim
Confidencemedium
Follow-upReconcile one-employee status with the "my team" claim.

Traction

Customer Status Table

Founder / internal team
The founder says the team uses Paca daily on Hacker News.
No proofClaim onlyUnknownUnknownUnknownlow

Google Search and company-controlled public surfaces were checked and showed no external production customer logos, case studies, or deployment references. These absences carry medium weight because they separate launch interest from real adoption.

Traction Signals

Roughly 967 to 988 GitHub stars and 55 to 57 forks.
source-backed facthigh
SourcePaca GitHub repository Paca GitHub releases
Active deployment and retained-user data.
171 points and 62 comments on Hacker News.
source-backed facthigh
SourceHacker News
Conversion from launch attention to retained users or paid pilots.
Near-daily v0.4.x releases in mid-June.
source-backed facthigh
SourcePaca GitHub releases
Sustained cadence after launch and quality under real usage.
Founderland published a launch article echoing Paca's story.
medium
SourceFounderland
Independent customers or quotes, not repeated launch metrics.

Product Hunt and Crunchbase were checked and showed no matching listing or company profile. These absences carry little weight for early-stage companies.

Hiring And Org Momentum

LinkedIn company
source-backed factOne employee and self-employed company type were visible.
SourcePaca LinkedIn company page
Public footprint looks like a solo or micro-team launch.
GitHub organization
source-backed factPublic organization page shows repositories but no public member roster.
SourcePaca GitHub organization
Public technical footprint does not resolve team size.

Indeed, Glassdoor, LinkedIn Jobs, and the Paca website were checked and showed no matching job postings or careers page. These absences carry little weight since job boards are often incomplete, and employee sentiment remains unavailable.

Role-mix read: No role mix is visible because no public roles were found.
Momentum read (growth / steady / contraction / unknown): unknown; the public record shows active product shipping but no public organization growth.

Traction Quality Read

Traction Dimension	Current Status	Good Enough For First Call?	Needed For Deep Diligence
Launch attention	Strong for an early open-source launch.	Yes, as a reason to take a cheap call.	Retention after the launch spike and channel conversion.
Production usage	Not public.	No.	Telemetry, references, active instances, or support records.
Revenue	Not public and likely zero under current free positioning.	No.	Paid pilots, hosted waitlist, contracts, or support revenue.
Community compounding	Early and unproven.	Only as a watch item.	Sustained non-bot contributors and third-party plugins.
Hiring and sales	No public signal.	No.	Named team and commercial owner.

Competitive Landscape

Segment	Examples	Customer Alternative	Pressure On Company
Incumbent work management	Atlassian Jira, monday.com, ClickUp	Stay with a suite that already has distribution, administration, and AI features.	Paca must offer a self-hosted or agent-control need incumbents do not serve.
Modern developer SaaS	Linear	Use a polished cloud product with agents and low per-seat pricing.	Paca must beat convenience, not just price.
Open-source project management	Plane, OpenProject, Taiga, Huly	Use a more established open-source alternative.	Paca must prove agent-native differentiation and community growth.
AI-native and Model Context Protocol peers	Multica, Agiflow	Choose a product already positioned around human-plus-agent work or MCP-native project context.	Paca must explain why its board, security, and self-hosting are superior.
Agent-workflow substitutes	beads, GitHub Issues, OpenHands	Combine existing issue tracking with agent tooling.	Paca must show the full PM layer adds enough value to justify adoption.

Category Visibility Snapshot

Google Search / United Statesbest Jira alternatives 2026 Linear ClickUp Plane

Captured page-one results (2026-06-17): Plane, Reddit, monday.com comparison content, and listicles appeared prominently.
Was the company present?: —

Google Search / United StatesAI native project management MCP Jira alternative

Captured page-one results (2026-06-17): Agiflow, Atlassian MCP-related results, Plane content, GitHub topics, and listicles appeared.
Was the company present?: —

Google Search / United Statesbest open source Jira alternative AI agents Scrum

Captured page-one results (2026-06-17): GitHub topics, Plane, OpenProject-related and listicle results appeared.
Was the company present?: —

Google Search / United Statesbest AI native Jira alternative open source self hosted

Captured page-one results (2026-06-17): Reddit, Plane, OpenProject, and open-source listicles appeared.
Was the company present?: —

AI assistant answer snapshotBest OSS Jira alternatives with AI agents for Scrum teams 2026

Captured page-one results (2026-06-17): Plane, OpenProject, Taiga, and related open-source tools were named in the parsed answer.
Was the company present?: —

Google Search in the United States was checked across category queries for Jira alternatives and AI-native project management; Paca did not appear in page-one results. These absences carry little weight for an early-stage open-source launch because discovery often lags developer-channel attention.

Visibility read (inference, low confidence): Paca has launch attention in developer channels, but category discovery still belongs to older open-source alternatives, incumbent AI pages, and AI-native peers. Visibility is not market share.

Pricing And Competitive Benchmark

Alternative	What It Offers	Public Price Signal	Price Vs. This Company	Evidence Label
Paca	Self-hosted AI-native project-management tool.	"Free forever"; no paid SKU public.	Baseline is zero, but operator hosting and large-language-model costs remain outside the price.	`company claim` via Paca homepage.
Jira	Incumbent agile project management with AI features.	Standard and Premium paid per-seat tiers are public.	Jira is paid but includes enterprise trust and distribution.	`company claim` via Jira pricing.
Linear	Developer project-management SaaS with agent positioning.	Free, Basic, and Business tiers are public.	Linear charges for convenience and workflow maturity.	`company claim` via Linear pricing.
ClickUp	Broad work-management suite.	Free tier and paid tiers are public.	ClickUp competes on breadth and low per-seat pricing.	`company claim` via ClickUp pricing.
OpenProject	Open-source project management with paid enterprise.	Free community plus paid enterprise pricing.	OpenProject proves self-hosted PM can attach enterprise monetization.	`company claim` via OpenProject pricing.

Price positioning read: Paca's zero price is attractive for adoption but not yet investable because price is not the same as value capture.
Price claims to correct or substantiate: Any claim that Paca is "free" should be paired with the operator's hosting and large-language-model cost and with the founder's intended paid layer, if one exists.

Competitive Wedge

Paca's potential wedge is the combination of self-hosted control, agents as first-class project participants, a built-in Model Context Protocol server, and a plugin system. That could matter to technical teams that want agent workflows without sending project context into an incumbent cloud. The wedge remains copyable until Paca shows production users choosing it for this exact reason, and until the security and value-capture model is stronger than "good open-source artifact."

Risks And Open Questions

Risk	Severity	Evidence	What To Ask
No durable value capture	Critical	Paca homepage, Paca GitHub repository, and Paca roadmap show free positioning and only exploratory hosted cloud.	What will Paca sell, who pays, and when?
No independent deployment proof	Critical	Public record shows stars and Hacker News attention, not customer-controlled usage.	Who outside the founder's own team runs Paca in production?
Solo-founder bus factor	High	Paca LinkedIn company page shows one employee; see hiring footnote under Hiring And Org Momentum.	Who else is full-time and who owns commercial, support, and security work?
Incumbent absorption	High	Atlassian Jira AI, Atlassian Rovo, Linear, Multica, and Agiflow overlap the narrative.	What buyer requirement makes Paca structurally different?
Security and supply-chain surface	High	Paca MCP setup guide, Paca plugin overview, and Paca deploy guide expose the agent, plugin, and install surfaces.	Has the sandbox, agent perimeter, and artifact integrity model been independently tested?

Pre-Mortem: The Most Likely Obituary

Cause of death: Paca never became a company because it stayed a beloved free open-source artifact while launch attention decayed, no paid layer or commercial owner appeared, and incumbents absorbed the agent-workflow narrative.
The causal chain: First, the founder keeps optimizing for craft and adoption instead of capture. Second, stars and Hacker News attention fail to convert into production deployments. Third, Atlassian, Linear, Multica, Agiflow, Plane, or other alternatives normalize agent workflows inside stronger distribution. Fourth, the solo-founder capacity limit slows security, support, and enterprise readiness. Fifth, the repository remains useful but economically uncaptured.
The earliest observable warning sign: At the next checkpoint, public interest rises or holds while deployments, hiring, and monetization remain absent.
The question that defuses this chain today: Do you intend to raise capital and build a company with a named, dated value-capture layer and commercial owner, or maintain an open-source project?

Decision-Critical Unknowns

Unknown	Why It Is Decision-Critical	Best Evidence	Decision Effect
Monetization intent	It determines whether the category size matters to Paca.	Founder-stated paid layer, dated SKU, paid pilots, or explicit no-monetization intent.	A credible plan moves toward pursue; a free-forever-only answer moves to pass.
Independent deployment	It separates developer attention from real demand.	Named production team, telemetry, Docker pulls, active project counts, or support tickets.	A reference strengthens the hold; no proof after the call moves toward pass.
Team capacity	It determines whether the founder can build, sell, secure, and support the product.	Org chart, committed contributors, hiring plan, and financing.	A team plan supports diligence; confirmed solo status with no commercial plan moves toward pass.
Security validation	It determines whether the plugin and agent thesis is safe enough for enterprise use.	Independent audit, threat model, signing, and scoped agent controls.	Strong controls remove an overhang; material unremediated issues trigger pass.
Defensibility	It determines whether Paca is a company or an incumbent feature.	Head-to-head wins and a buyer requirement incumbents cannot serve.	Structural proof supports pursue; parity with no demand supports pass.

Diligence Questions

First Call

Question	Why It Matters	Good Evidence
What paid product will you ship, what stays free, and who owns the commercial plan?	This is the single highest-leverage value-capture question.	Dated plan, free-versus-paid boundary, owner, and early willingness-to-pay evidence.
How many production instances run outside your own team?	This validates demand beyond launch interest.	Telemetry, Docker pulls, references, active projects, or support tickets.
Who is full-time besides you?	This resolves bus factor and company-building capacity.	Org chart, payroll or commitments, recruiting plan, and role ownership.
Why will a team choose Paca instead of Jira, Linear, Plane, Multica, Agiflow, or GitHub Issues plus agent tooling?	This tests whether the wedge is structural.	Buyer interviews, win-loss notes, and a head-to-head matrix.
What has been independently tested in the plugin sandbox and agent action model?	This tests the safety of the core technical thesis.	Audit, threat model, signed artifacts, scoped permissions, and remediation owner.

Follow-Up

Question	Why It Matters	Good Evidence
What is the cap table, runway, and raise plan?	This determines whether the fund can enter and whether the company can staff the plan.	Cap table, SAFE or round terms, runway, and use of funds.
What happened to earlier founder-associated projects?	This tests follow-through and learning from prior builds.	User metrics, shutdown notes, app links, or post-mortems.
What does Paca cost to operate at scale with external large-language-model providers?	This tests whether "free" remains compelling after inference costs.	Benchmarks, provider options, local-model roadmap, and spend caps.
What enterprise controls will ship before any paid rollout?	This tests procurement readiness.	Dated milestones for role-based access, single sign-on, audit logs, scoping, and support commitments.

Kill Criteria

Kill Criterion	Evidence That Would Trigger It
Free-forever-only intent	The founder confirms no monetization, no hosted or enterprise layer, no support model, and no fundraising intent.
Adoption without demand	Stars, forks, and community discussion continue, but deployments, hiring, and revenue remain absent at the next checkpoint.
Solo maintainer with no commercial plan	The founder confirms no committed team, no hiring intent, no commercial owner, and no capital to staff the missing functions.
Incumbent or peer absorption	Atlassian, Linear, Multica, Agiflow, or Plane matches the wedge while Paca has no self-hosted buyer proof.
Material unremediated security issue	A sandbox escape, static-key agent compromise, unsigned supply-chain incident, or equivalent risk appears without a remediation owner.

Double-Down Criteria

Double-Down Criterion	Evidence That Would Justify More Diligence
Dated value-capture layer	A founder-owned plan defines hosted, enterprise, support, marketplace, or usage-based monetization with a free-versus-paid boundary.
Independent production demand	At least one referenceable production team or credible deployment telemetry validates real usage.
Team capacity	A commercial owner, security owner, or credible hire/financing plan appears.
Structural wedge	A buyer chooses Paca for self-hosted agent control or data sovereignty in a way incumbents will not serve.
Compounding ecosystem	Non-bot contributors, third-party plugins, integrations, and deployments grow over multiple quarters.

Founder Action Plan

Timeframe	Action	Output
Before the next investor conversation	Decide and write the free-versus-paid boundary and value-capture mechanism.	One-page monetization plan with timeline, buyer, owner, and pricing hypothesis.
Before the next investor conversation	Produce one independent demand signal.	Telemetry screenshot, Docker pull data, named production reference, or paid-pilot record.
Before the next investor conversation	Reconcile team size and ownership.	Org chart, full-time status, contributor commitments, and hiring plan.
Next sprint	Build the head-to-head wedge memo.	Comparison against Jira with Rovo, Linear, Plane, Multica, Agiflow, and GitHub Issues plus agent tooling.
Next sprint	Start security proof.	Threat model, external audit plan, artifact-signing plan, and scoped-agent control plan.
Next 1-2 quarters	Show compounding, not launch attention.	Trendline of deployments, non-bot contributors, third-party plugins, retained users, and early paid intent.
Next 1-2 quarters	Clarify financing path.	Cap table, runway, raise plan, and use-of-funds tied to commercial and security hires.

Decision

Screen: hold, pass-leaning.
Confidence: medium.
Rationale: The builder and category are interesting enough for one cheap founder call, but not enough for a check because value capture, independent demand, team capacity, and defensibility remain unresolved.
What would move this to pursue: A dated value-capture layer, an independent production deployment signal, and a credible commercial or hiring plan would make deeper diligence rational.
What would move this to pass: A free-forever-only answer, no independent deployment proof after the call, confirmed solo-maintainer status with no commercial plan, or a material security issue would end the opportunity.
Recommended next step: Run one 60-minute founder call with the questions above and decide within one week of receiving the proof packet.
Founder preparation standard: Bring evidence, not narrative; the call should resolve monetization intent, demand proof, team capacity, security readiness, and competitive wedge.

How We Would Miss This One

The miss scenario: Paca could be the one that got away if the founder is a rare technical founder at the start of a new agent-native work-management category, chooses a GitLab-style capture layer quickly, and turns self-hosted agent control into a buyer requirement before incumbents can respond.
Flip conditions: A dated paid layer, one referenceable deployment, a commercial or security hire, and early ecosystem compounding would flip the current pass-leaning hold into active pursuit.
Revisit trigger / date: Revisit immediately after the founder call if the proof packet lands, or by 2026-09-17 if public evidence shows a paid layer, deployment references, and team expansion.

Source Log

Paca homepage
paca-ai.org
Product positioning, self-hosted and free claims.
Retrieved 2026-06-17Company-controlled page.high
Paca GitHub repository
github.com
Repository, product surface, stars, commits, license pointer, installation, and stack.
Retrieved 2026-06-17Company-controlled platform and platform metric.high
Paca license
github.com
Apache-2.0 license terms.
Retrieved 2026-06-17License file.high
Paca roadmap
github.com
Hosted cloud exploration and planned enterprise controls.
Retrieved 2026-06-17Technical roadmap.high
Paca GitHub releases
github.com
Release cadence and same-day star snapshot.
Retrieved 2026-06-17Company-controlled platform metric.high
Hacker News Show HN thread
news.ycombinator.com
Launch attention, founder narrative, and community peer comparisons.
Retrieved 2026-06-17Community platform and founder statement.high
Hải Huỳnh GitHub profile
github.com
Founder identity, location, and public GitHub footprint.
Retrieved 2026-06-17Public profile.high
Hải Huỳnh GitHub repositories
github.com
Prior public repositories and technical footprint.
Retrieved 2026-06-17Public profile.high
Hải Huỳnh LinkedIn profile
linkedin.com
Founder identity, education claim, company association, and avatar source.
Retrieved 2026-06-17Public profile dataset.medium
Paca LinkedIn company page
linkedin.com
Company headcount and launch-post signal.
Retrieved 2026-06-17Company profile dataset.medium
Paca GitHub organization
github.com
Public organization footprint and repositories.
Retrieved 2026-06-17Company-controlled platform.high
Paca architecture overview
github.com
Technical architecture, service dependencies, and OpenHands runtime.
Retrieved 2026-06-17Technical documentation.high
Paca deploy guide
github.com
Installation, secrets, and deployment surface.
Retrieved 2026-06-17Technical documentation.high
Paca getting started guide
github.com
Installation and API-key setup.
Retrieved 2026-06-17Technical documentation.high
Paca security policy
github.com
Vulnerability disclosure and in-scope security classes.
Retrieved 2026-06-17Security page.high
Paca plugin overview
github.com
WebAssembly plugin model, marketplace, and sandbox claims.
Retrieved 2026-06-17Technical documentation.high
Paca MCP setup guide
github.com
Model Context Protocol server, static API key, and tool surface.
Retrieved 2026-06-17Technical documentation.high
Founderland launch article
founderland.ai
Third-party launch visibility and repeated public metrics.
Retrieved 2026-06-17Third-party article.medium
Atlassian annual report
s206.q4cdn.com
Public-company revenue, customers, gross margin, and AI context.
Retrieved 2026-06-17Public-company filing.high
Asana annual report
materials.proxyvote.com
Public-company revenue, gross profit, and customer count.
Retrieved 2026-06-17Public-company filing.high
monday.com annual report
sec.gov
Public-company revenue, customer count, Work OS framing, and AI context.
Retrieved 2026-06-17Public-company filing.high
GitLab annual report
s204.q4cdn.com
Open-core precedent, revenue, gross margin, and contributor context.
Retrieved 2026-06-17Public-company filing.high
Jira pricing
atlassian.com
Seat-pricing benchmark.
Retrieved 2026-06-17Company-controlled pricing page.medium
Asana pricing
asana.com
Seat-pricing and AI add-on benchmark.
Retrieved 2026-06-17Company-controlled pricing page.medium
monday.com pricing support
support.monday.com
Work OS pricing structure.
Retrieved 2026-06-17Company-controlled support page.medium
OpenProject pricing
openproject.org
Open-source community and paid enterprise benchmark.
Retrieved 2026-06-17Company-controlled pricing page.medium
Linear pricing
linear.app
Developer SaaS pricing benchmark.
Retrieved 2026-06-17Company-controlled pricing page.high
ClickUp pricing
clickup.com
Work-management pricing benchmark.
Retrieved 2026-06-17Company-controlled pricing page.high
Research Nester project management software market
researchnester.com
Top-down project-management market-size lead.
Retrieved 2026-06-17Market-sizing aggregator.low
Market Research Future project management software market
marketresearchfuture.com
Top-down project-management market-size lead.
Retrieved 2026-06-17Market-sizing aggregator.low
Technavio AI in project management market
technavio.com
AI-in-project-management growth lead.
Retrieved 2026-06-17Market-sizing aggregator.low
Research and Markets AI in project management market
researchandmarkets.com
AI-in-project-management market-size lead.
Retrieved 2026-06-17Market-sizing aggregator.low
PMI global project management talent gap
pmi.org
Project-professional denominator.
Retrieved 2026-06-17Trade association.medium
PMI shaping the future of project management with AI
pmi.org
AI adoption gap among project professionals.
Retrieved 2026-06-17Trade association.medium
BLS software developers, quality assurance analysts, and testers
bls.gov
United States software developer and quality-assurance workforce denominator.
Retrieved 2026-06-17Government statistics.high
GitHub Octoverse 2025
github.blog
Developer ecosystem and AI development context.
Retrieved 2026-06-17Company-controlled platform report.medium
Atlassian Jira
atlassian.com
Incumbent Jira positioning and AI-agent overlap.
Retrieved 2026-06-17Company-controlled product page.high
Atlassian Jira AI
atlassian.com
Agentic Jira positioning.
Retrieved 2026-06-17Company-controlled product page.high
Atlassian Rovo
atlassian.com
Incumbent agent product.
Retrieved 2026-06-17Company-controlled product page.high
Atlassian Rovo agents documentation
support.atlassian.com
Rovo agent capabilities.
Retrieved 2026-06-17Technical documentation.high
Linear homepage
linear.app
Modern developer SaaS and teams-with-agents positioning.
Retrieved 2026-06-17Company-controlled product page.high
ClickUp homepage
clickup.com
Work-management suite positioning.
Retrieved 2026-06-17Company-controlled product page.high
monday.com homepage
monday.com
Work OS and AI positioning.
Retrieved 2026-06-17Company-controlled product page.high
Plane homepage
plane.so
Open-source project-management competitor positioning.
Retrieved 2026-06-17Company-controlled product page.high
Plane GitHub repository
github.com
Open-source adoption benchmark.
Retrieved 2026-06-17Platform metric.high
OpenProject homepage
openproject.org
Open-source enterprise project-management positioning.
Retrieved 2026-06-17Company-controlled product page.high
OpenProject GitHub repository
github.com
Open-source adoption benchmark.
Retrieved 2026-06-17Platform metric.high
Taiga homepage
taiga.io
Open-source agile project-management positioning.
Retrieved 2026-06-17Company-controlled product page.high
Taiga GitHub repository
github.com
Open-source adoption benchmark.
Retrieved 2026-06-17Platform metric.medium
Huly homepage
huly.io
Open-source all-in-one competitor positioning.
Retrieved 2026-06-17Company-controlled product page.high
Huly GitHub repository
github.com
Open-source adoption benchmark.
Retrieved 2026-06-17Platform metric.high
Multica homepage
multica.ai
Human-plus-agent project-management peer.
Retrieved 2026-06-17Company-controlled product page.high
Multica GitHub repository
github.com
Open-source peer repository.
Retrieved 2026-06-17Company-controlled platform.medium
Agiflow Jira alternative
agiflow.io
Model Context Protocol-native project-management peer.
Retrieved 2026-06-17Company-controlled product page.high
beads GitHub repository
github.com
Agent issue-tracker substitute and adoption proxy.
Retrieved 2026-06-17Company-controlled platform and platform metric.high
GitHub Issues
github.com
Platform issue-tracking substitute.
Retrieved 2026-06-17Company-controlled product page.high
OpenHands homepage
openhands.dev
Coding-agent platform and Paca runtime dependency context.
Retrieved 2026-06-17Company-controlled product page.high

Access limitations: Public research did not include Paca's private telemetry, cap table, bank or billing records, deployment analytics, customer references, private roadmap, security audits, or founder interview answers. Absence checks through Google Search, Product Hunt, Crunchbase, LinkedIn Jobs, Indeed, and Glassdoor are not exhaustive. Search-result and AI-assistant visibility snapshots were treated as low-confidence visibility signals and excluded from the Source Log unless a client-safe public page was separately available. These limitations mean the report can identify the decisive gaps but cannot prove Paca has no private users, no private financing, or no internal monetization plan.

Public disclaimer: This is an independent public teardown based solely on publicly available information retrieved on 2026-06-17. It is research support, not investment, legal, tax, or financial advice. Company-provided statements are labeled as claims, not verified facts. Paca did not participate in or review this report. Errors and omissions are possible; final decisions remain with the reader.

What The Company Does#

Key Takeaways#

What Makes This Potentially Fundable#

The Four Holes To Close Before Fundraising#

Decision Snapshot#

IC Disagreement Map#

Scenario Range#

What Investors Will Test#

Claim Reconciliation: Inconsistencies Investors Will Catch#

Diligence Findings: Issues To Fix Before You Raise#

Data Room Readiness Checklist#

First-Call Agenda For The Startup#

Business Model And Revenue Signals#

Revenue Quality Checklist#

Funding And Ownership Context#

Founder, Team, And Related Entities#

Founder And Team#

Founder Competency Coverage#

Public Professional Footprint#

Founder-Market Fit Read#

Related Entities And Founder-Associated Companies#

Traction#

Customer Status Table#

Traction Signals#

Hiring And Org Momentum#

Traction Quality Read#

Competitive Landscape#

Category Visibility Snapshot#

Pricing And Competitive Benchmark#

Competitive Wedge#

Risks And Open Questions#

Pre-Mortem: The Most Likely Obituary#

Decision-Critical Unknowns#

Diligence Questions#

First Call#

Follow-Up#

Kill Criteria#

Double-Down Criteria#

Founder Action Plan#

Decision#

How We Would Miss This One#

Source Log#