Skip to content

feat: implement browser-ready intent factory and initialize project d… #103

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
purushpsm147 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

feat: implement browser-ready intent factory and initialize project d… #103

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
02210ba
feat: implement browser-ready intent factory and initialize project d…
purushpsm147 Apr 15, 2026
0770171
chore: update package-lock.json dependencies
purushpsm147 Apr 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions Generate blueprint json/BaselineBluePrint.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,21 @@ Because the engine evaluates strictly on the client side without cross-session e

**Blueprints** solve this cold-start problem. By injecting a pre-calculated mathematical topography into the engine on Day 1, developers can achieve instant, zero-latency intent detection from the very first user session.

## When to Use Blueprints vs. Custom Consolidation

**Blueprints are the right starting point** when a team has short sessions but a
fairly standard journey. A startup or mid-market ecommerce team can inject
`ecommerce-strict-funnel.json`, start with mature prior transition counts, and
get usable confidence immediately while the engine continues adapting to its own
traffic.

**Custom consolidation becomes valuable** when the customer journey is highly
specialized. Enterprise teams with bespoke B2B checkout, approval, onboarding,
or regulated intake flows often need a baseline that reflects their exact path,
not a generic template. In those cases, a customer-specific blueprint plus the
Persistent Graph Consolidator lets the engine preserve learning across short
sessions and keep improving without depending on a single long visit.

---

## The Blueprints
Expand Down
51 changes: 45 additions & 6 deletions PRICING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,12 +13,45 @@ PassiveIntent is **free and open-source** under AGPLv3 for open-source projects,

## Tiers

| Tier | Annual Fee | Target Audience | What You Get (Support & Features) |
| ---------- | ---------- | ------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Free | $0 | Open-source projects, students | AGPLv3 copyleft license. Full SDK. **Support:** Community Forum / GitHub Issues only. |
| Startup | $599/yr | Small teams (5–50 employees) | Up to 3 Commercial Projects, AGPL exemption. **Support:** Priority Email Support — async, business days only. |
| Growth | $1,999/yr | Scaling companies (50–200 employees) | Unlimited Internal Projects (1 org). **Support:** Direct Founder Access — async email/chat, business days only. |
| Enterprise | Custom | Multi-org deployments, highly regulated industries (Fintech/Healthcare), and massive retail operations. | Unlimited scope. Includes AGPL commercial exemption, OEM wrapping rights, and white-labeling. **Premium Intent Catalog:** Access the private `@passiveintent/enterprise` NPM package (Fraud, VIP Whale, Rage-Quit detection — subject to request). **Custom Integration Sprints:** We build domain-specific kinematic adapters for your exact UI. **Zero-Trust BYOC:** Custom telemetry egress adapters routed directly to your private AWS/Azure/GCP VPC, bypassing third-party analytics. **Support:** Dedicated private Slack Connect channel — direct line to the engineer who built this. Priority issue triage before all other tiers. Quarterly roadmap review call included. Weekend/24-7 coverage available upon request at additional cost. |
### Free

Annual Fee: **$0**

Target Audience: Open-source projects and students.

What You Get: AGPLv3 copyleft license and the full SDK. Support is limited to the Community Forum and GitHub Issues.

### Startup

Annual Fee: **$599/yr**

Target Audience: Small teams with roughly 5 to 50 employees.

What You Get: Up to 3 commercial projects, AGPL exemption, and priority email support during business days.

### Growth

Annual Fee: **$1,999/yr**

Target Audience: Scaling companies with roughly 50 to 200 employees.

What You Get: Unlimited internal projects within one organization and direct founder access over async email and chat during business days.

### Enterprise

Annual Fee: **Custom**

Target Audience: Multi-org deployments, highly regulated industries such as fintech and healthcare, and massive retail operations.

What You Get: Unlimited scope, AGPL commercial exemption, OEM rights, white-labeling, premium enterprise modules, custom integration sprints, Persistent Graph Consolidator access, BYOC egress options, and dedicated support.

Enterprise packages can additionally include:

- Premium Intent Catalog access via the private `@passiveintent/enterprise` package.
- Customer-specific kinematic adapters and integration sprints for your exact UI.
- Persistent Graph Consolidator engagements for cross-session learning in short-session, high-consideration funnels.
- Zero-Trust BYOC telemetry routing directly into your private AWS, Azure, or GCP environment.
- Dedicated Slack Connect support, priority triage, roadmap reviews, and optional expanded coverage.

## What "commercial use" means

Expand Down Expand Up @@ -53,6 +86,12 @@ A single deployable web application or npm package that ships PassiveIntent. Mic
**Is there a trial period?**
The Free (AGPLv3) tier has no time limit and no feature restrictions — it is the full SDK. Commercial tiers add a support channel, AGPL exemption, and (for Growth/Enterprise) premium features as they ship.

**We have short user sessions. Should we start with a Blueprint or an Enterprise engagement?**
If your flow broadly matches a standard ecommerce or content journey, start with a Blueprint JSON. It seeds the engine with mature prior transition counts on day one and is usually the fastest way to bypass cold start for startup and growth-stage teams. If your journey is highly customized and users only generate a small number of events per session, a generic blueprint can be too coarse. In that case, we recommend an Enterprise engagement with the Persistent Graph Consolidator so the model can preserve learning across sessions and tune itself to your exact funnel. Engagements start at **$50,000**.

**What changes when we outgrow the generic Blueprint?**
The open-source path is designed to deliver immediate value with synthetic baselines and live-session memory. That is often enough to catch hesitation and recover abandoned carts quickly. Teams typically move up when they want the engine to stop resetting to a generic prior and start retaining the organic behavior of their own customers over a longer window. That is the role of the Enterprise package: Persistent Graph Consolidator preserves customer-specific learning across sessions, supports long-horizon calibration, and keeps the model compounding instead of restarting.

---

## Support Boundaries
Expand Down
11 changes: 6 additions & 5 deletions landing/cheatsheet.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -177,13 +177,14 @@ <h1>One page that connects the math to the marketing move.</h1>
<span class="cheatsheet-mandate-label">Important note on thresholds</span>
<h3 data-cheatsheet-mandate-title>Propensity thresholds are not universal constants.</h3>
<p data-cheatsheet-mandate-summary>
A 3-page checkout funnel and a 40-page discovery catalog have entirely different
structural probabilities.
A 3-page checkout funnel and a 40-page discovery catalog have different structural
probabilities, and organic learning depends on your privacy and storage mode.
</p>
<p data-cheatsheet-mandate-detail>
The thresholds below assume a calibrated baseline tuned to your site's traffic patterns.
For best accuracy, ensure your integration includes a calibration step before you apply
hard intervention rules in production.
The engine starts from raw Markov probabilities. In zero-consent, ephemeral deployments,
it resets with the tab, so Blueprint JSON is the practical path to instant,
high-sensitivity funnel enforcement. Teams that want cross-session organic learning can
enable compliant persistent storage or move to Enterprise Persistent Graph Consolidator.
</p>
</div>

Expand Down
7 changes: 4 additions & 3 deletions landing/ecommerce/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@
"name": "Does PassiveIntent require cookie banners to work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. PassiveIntent calculates intent locally in the browser without exporting behavioral payloads to PassiveIntent servers."
"text": "For the default zero-egress, in-memory deployment, no. If you enable persistent browser storage or export graph data to your own infrastructure, your consent and privacy obligations depend on your implementation and legal review."
}
},
{
Expand Down Expand Up @@ -894,8 +894,9 @@ <h2>What eCommerce teams ask before they install.</h2>
<details>
<summary>Does PassiveIntent require cookie banners to work?</summary>
<p>
No. PassiveIntent runs locally in the browser and does not export behavioral payloads
to our servers.
For the default zero-egress, in-memory deployment, no.* If you enable persistent
browser storage or export graph data to your own infrastructure, your consent and
privacy obligations depend on your implementation and legal review.
Comment on lines +897 to +899
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Apr 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Align the rest of the page with this new compliance caveat.

This FAQ now correctly makes banner/privacy obligations conditional, but the same page still says “No banner. No sensors. No PII export.” at Line 826. Leaving both claims in one page gives readers conflicting compliance guidance and undermines the clarification this PR is adding.

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@landing/ecommerce/index.html` around lines 897 - 899, Update the conflicting
FAQ statement that currently reads "No banner. No sensors. No PII export." so it
matches the new conditional compliance caveat: make the claim conditional for
the default zero-egress in-memory deployment and add a qualifier that persistent
browser storage or exporting graph data may create additional consent/privacy
obligations; locate and edit the HTML node containing that exact phrase ("No
banner. No sensors. No PII export.") and replace it with a conditional sentence
consistent with the paragraph referencing the default zero-egress behavior.

</p>
</details>
<details>
Expand Down
26 changes: 15 additions & 11 deletions landing/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@
"name": "Do we need a cookie banner for PassiveIntent to work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. PassiveIntent itself does not require analytics cookies or server-side behavioral tracking."
"text": "For the default zero-egress, in-memory deployment, no. If you enable persistent browser storage or export graph data to your own infrastructure, your consent and privacy obligations depend on your implementation and legal review."
}
},
{
Expand Down Expand Up @@ -694,9 +694,10 @@ <h3>Calibration guide</h3>
<p class="eyebrow">Open-source core vs enterprise</p>
<h2>Start with the pure core. Expand when the journey gets bigger.</h2>
<p class="section-copy">
The AGPL core is built for one live session on one site in one tab. Enterprise is for
The AGPL core is built for one live session on one site in one tab. Start with a
Blueprint when the journey is standard and sessions are short. Enterprise is for
brands that need continuity across repeat visits, connected properties,
comparison-heavy journeys, and high-volatility campaigns.
customer-specific funnels, and high-volatility campaigns.
</p>
</div>

Expand Down Expand Up @@ -743,8 +744,9 @@ <h2>Start with the pure core. Expand when the journey gets bigger.</h2>

<div class="enterprise-compare-footer">
<p>
<strong>Same privacy promise.</strong> Enterprise keeps the zero-egress posture of the
core while widening the kinds of journeys you can understand.
<strong>Same privacy promise.</strong> Start with a Blueprint when the journey is
standard. Move to enterprise when the model needs to retain organic customer learning
across visits, tabs, or properties.
</p>
<div class="cta-actions enterprise-compare-actions">
<a class="btn btn-primary" href="./licensing.html#offerings-compare"
Expand Down Expand Up @@ -803,8 +805,8 @@ <h3>Growth</h3>
<h3>Enterprise</h3>
<p class="price price-custom">Custom</p>
<p>
Built for repeat visits, connected properties, comparison-heavy journeys, and
enterprise rollout needs.
Built for repeat visits, connected properties, and custom short-session journeys that
need cross-session continuity and long-term customer-specific calibration.
</p>
<a
class="btn btn-secondary"
Expand Down Expand Up @@ -862,8 +864,9 @@ <h2>What teams usually need answered before they adopt.</h2>
<details>
<summary>Do we need a cookie banner for PassiveIntent to work?</summary>
<p>
No. PassiveIntent itself does not require analytics cookies or server-side behavioral
tracking.
For the default zero-egress, in-memory deployment, no.* If you enable persistent
browser storage or export graph data to your own infrastructure, your consent and
privacy obligations depend on your implementation and legal review.
</p>
</details>
<details>
Expand All @@ -879,8 +882,9 @@ <h2>What teams usually need answered before they adopt.</h2>
</summary>
<p>
PassiveIntent Core is the AGPL open-source engine for one live session on one site in
one tab. Enterprise expands that same privacy-first model for repeat visits, connected
properties, tab-heavy research, and fast-changing traffic conditions.
one tab. If a standard journey only needs a faster start, use a Blueprint. Enterprise
expands that same privacy-first model for repeat visits, connected properties,
customer-specific short-session funnels, and fast-changing traffic conditions.
</p>
</details>
<details>
Expand Down
Loading
Loading