Version: 2.0 Last Updated: March 2026 Status: Planning Domain: varax.io (secured) Relationship: Companion document to the Varax Compliance Automation Platform PRD v3.0
- Executive Summary
- Naming & Domain Strategy
- Two-Product Brand Strategy
- Goals & Success Metrics
- Target Audiences
- Site Architecture
- Page-by-Page Specifications
- Varax Monitor Section
- Conversion Funnels
- Content Marketing Hub
- SEO Strategy
- Technical Stack & Hosting
- Design Principles
- Email Capture & Nurture
- Stripe Integration & Purchase Flow
- Analytics & Tracking
- Legal & Compliance Pages
- Launch Phases
- Open Questions
The marketing website is the central hub for the entire go-to-market strategy. It's the home for two products under one brand: Varax Monitor, the free, open-source CronJob monitoring tool (the community builder), and Varax, the commercial Compliance Platform (the revenue driver). It serves four critical functions: showcasing the free tool to build trust and community, converting open-source users into paying compliance customers, establishing credibility in the Kubernetes space, and capturing leads through content marketing.
This is not a web app — it's a marketing, documentation, and content site with a Stripe-powered purchase flow. Both products are CLI/operator tools installed via Helm. The website sells, educates, and converts.
Two-product strategy on one site: Varax Monitor gets its own dedicated section — not buried as a footnote, but elevated as a genuine product that demonstrates Kubernetes expertise. Users who discover the free tool and trust the brand are the highest-quality leads for the compliance platform. The website architecture reflects this funnel: free tool → trust → compliance need → paid product.
Key principle: DevOps engineers and platform engineers are the audience. They are skeptical of marketing fluff, responsive to technical depth, and make purchasing decisions based on documentation quality, sample output, and peer trust (GitHub stars, community adoption). The site must feel like a developer tool's homepage, not a SaaS landing page.
| Element | Name | Status |
|---|---|---|
| Company / Brand | Varax | Confirmed |
| Compliance Platform | Varax | Confirmed (flagship product shares the brand name) |
| OSS CronJob Monitor | Varax Monitor | Confirmed |
| Domain | varax.io | Secured |
- Primary domain:
varax.io— marketing site, docs, blog - GitHub org:
github.com/varax(orgithub.com/varax-ioif unavailable) - Email:
hello@varax.io,support@varax.io - DNS: Managed via Cloudflare (free tier sufficient)
- SSL: Automatic via hosting provider or Cloudflare
The compliance platform CLI uses the varax command directly:
varax scan
varax report
varax report --format pdf
Varax Monitor uses a separate Helm chart under the Varax org:
helm install varax-monitor varax/varax-monitor
| Varax Monitor | Varax Compliance Platform | |
|---|---|---|
| Role | Community builder, trust engine | Revenue driver |
| Price | Free forever (Apache 2.0) | Free tier + Pro at $149/mo |
| Purpose on website | Attract developers, demonstrate K8s expertise, build email list | Convert trust into revenue |
| Primary audience | Any K8s team with CronJobs | Teams needing SOC2 compliance |
| GitHub repo | varax/varax-monitor |
varax/operator |
Both products live under the Varax brand. The website presents them as a product suite from a team that deeply understands Kubernetes operations:
Varax
├── Varax Monitor — "Free Kubernetes CronJob monitoring. Zero config. Zero cost."
└── Varax — "Automated SOC2 compliance for Kubernetes. Scan, evidence, report."
- Shared credibility: GitHub stars and community trust from Varax Monitor directly benefit the compliance platform's perceived quality.
- SEO consolidation: One domain (varax.io) accumulates all authority. Blog posts about CronJobs and compliance both build the same domain's ranking.
- Simpler brand story: "We build Kubernetes tools" is clearer than managing two separate identities.
- Natural upgrade path: Users who find Varax Monitor discover the compliance tool on the same site. No redirect, no friction.
- Lower maintenance: One codebase, one deployment, one analytics setup.
The primary navigation gives Varax (the compliance platform) top billing as the revenue product, but Varax Monitor has its own dedicated section — not hidden in a footer link. The relationship should feel like how Hashicorp presents Terraform (free) alongside Vault (commercial) — both legitimate products, one ecosystem.
Users arriving for Varax Monitor should naturally encounter the compliance platform through:
- A persistent "Also from Varax" banner or nav element
- Blog posts that span both products ("Monitoring + Compliance: Your K8s Operations Checklist")
- The Varax Monitor page itself, with a tasteful (not aggressive) cross-promotion section
- Email nurture sequences that introduce Varax compliance to Varax Monitor users
- Convert open-source users to Pro subscribers — the website is where
varax reportupgrade prompts send users - Capture email leads from content marketing visitors
- Establish credibility as the Kubernetes compliance authority
- Provide documentation that makes installation and usage frictionless
| Metric | Month 1-3 | Month 4-6 | Month 7-12 |
|---|---|---|---|
| Monthly unique visitors | 500 | 2,000 | 5,000+ |
| Blog post pageviews/month | 1,000 | 5,000 | 15,000+ |
| Email list subscribers | 100 | 500 | 1,000+ |
| Pricing page visits | 50 | 300 | 1,000+ |
| Stripe checkout initiated | 5 | 20 | 50+ |
| Pro purchases completed | 2 | 8 | 20+ |
| Avg. time on docs pages | >3 min | >3 min | >3 min |
| Bounce rate (homepage) | <60% | <50% | <45% |
These align with the customer personas defined in the Varax Compliance PRD v3.0, but with website-specific behavioral context.
Who: DevOps/platform engineer who found the open-source repo on GitHub, Reddit, or Hacker News. Arrives at: Homepage or docs (via README links). Wants: To understand what the tool does beyond the README, see sample reports, and evaluate if it's worth installing. Conversion goal: Install the operator, eventually upgrade to Pro.
Who: Existing free-tier user who ran varax report and saw "Upgrade to Pro for full audit-ready reports."
Arrives at: Pricing page directly (the CLI links here).
Wants: To see exactly what Pro includes, view a sample report, and buy immediately.
Conversion goal: Purchase Pro license within that session.
Who: Engineer searching for "SOC2 for Kubernetes", "CIS benchmark Kubernetes", or "Kubernetes compliance automation." Arrives at: Blog post or guide. Wants: To solve a specific compliance problem. Doesn't know Varax yet. Conversion goal: Email capture, nurture, free install, Pro.
Who: Technical leader evaluating tools for their team. May have been forwarded a link by their DevOps engineer. Arrives at: Homepage or pricing page. Wants: ROI justification, credibility signals, and a clear understanding of what they're buying. Conversion goal: Approve the purchase or sign up for a consulting assessment.
varax.io/
├── / ........................... Homepage (hero, value prop, social proof, CTA)
├── /pricing ................... Pricing tiers, FAQ, purchase CTAs
├── /docs ...................... Documentation hub
│ ├── /docs/compliance/ ...... Varax compliance platform docs
│ │ ├── quickstart ......... 5-minute installation guide
│ │ ├── configuration ...... ComplianceConfig CRD reference
│ │ ├── scanning ........... Scanner details, check list
│ │ ├── reports ............ Report types, generation guide
│ │ ├── remediation ........ Auto-remediation guide
│ │ ├── soc2-mapping ....... Full SOC2 control mapping reference
│ │ └── faq ................ Technical FAQ
│ └── /docs/monitor/ ......... Varax Monitor docs
│ ├── quickstart ......... 60-second installation guide
│ ├── metrics ............ Prometheus metrics reference
│ ├── dashboards ......... Grafana dashboard setup
│ ├── alerts ............. Alert rules reference
│ └── faq ................ Technical FAQ
├── /monitor ................... Varax Monitor product page (dedicated landing)
├── /blog ...................... Content marketing hub
│ ├── /blog/[slug] ........... Individual blog posts
│ └── /blog/tags/[tag] ....... Tag-filtered views
├── /sample-report ............. Interactive sample SOC2 report (gated or ungated)
├── /consulting ................ SOC2 Readiness Assessment service page
├── /about ..................... About page (founder story, mission, open source commitment)
├── /changelog ................. Product changelog / release notes
├── /privacy ................... Privacy policy
├── /terms ..................... Terms of service
└── /404 ....................... Custom 404
Primary nav (persistent header):
[Varax Logo] Products ▾ Docs Pricing Blog GitHub [Get Started]
├── Varax Compliance
└── Varax Monitor (Free)
Footer:
Products Resources Company Legal
───────── ───────── ───────── ─────────
Varax Compliance Compliance Docs About Privacy Policy
Varax Monitor Monitor Docs Consulting Terms of Service
Pricing Blog GitHub
Sample Report SOC2 Mapping Contact
Changelog FAQ
The homepage must accomplish five things in order of priority:
- Communicate the value prop in <5 seconds — "What is this and why should I care?"
- Show, don't tell — sample report screenshot, terminal output, compliance score
- Establish credibility — GitHub stars, install count, community signals
- Provide two clear CTAs — "Install Free" and "View Sample Report"
- Address both engineers and decision-makers — technical depth for engineers, ROI for CTOs
The homepage leads with the Varax compliance platform (the revenue product) but prominently features Varax Monitor as proof of the brand's Kubernetes expertise.
[Tagline — one line, e.g. "Kubernetes tools that keep your clusters running and compliant."]
[Subheadline — e.g. "Open-source monitoring and compliance automation for Kubernetes.
From CronJob observability to audit-ready SOC2 reports — all Kubernetes-native, all self-hosted."]
[Primary CTA: "Explore Compliance"] [Secondary CTA: "Free Varax Monitor"]
[Hero visual: terminal screenshot showing `varax report` command generating a PDF,
or a split view of terminal + the resulting report]
[GitHub stars count] [Docker/GHCR pulls] [# of clusters monitored (opt-in telemetry)]
If early stage and numbers are low, replace with logos of frameworks/standards supported:
CIS Benchmark • NSA/CISA • SOC2 Trust Services • Pod Security Standards
Three steps, each with a code snippet or visual:
- Install —
helm install varax varax/operator(show terminal) - Scan —
varax scanoutput showing compliance score (show terminal) - Report —
varax report --format pdf→ PDF screenshot (show output)
Four to six key features, each with an icon and 1-2 sentence description:
- Auto-Discovery — Scans your entire cluster automatically. No configuration files to maintain.
- SOC2 Control Mapping — Every check maps to specific SOC2 Trust Services Criteria.
- Audit-Ready Reports — Generate the PDF your auditor needs with one CLI command.
- Auto-Enable Audit Logging — Programmatically enables K8s audit logging on EKS, AKS, and GKE.
- Auto-Remediation — Opt-in fixes for failing checks with dry-run mode.
- Zero External Dependencies — Runs entirely in your cluster. Your data never leaves.
| Varax | Kubescape | Vanta/Drata | |
|---|---|---|---|
| K8s-native operator | Yes | Yes | No |
| Audit-ready PDF reports | Yes | No | Yes (not K8s-specific) |
| Auto-enable audit logging | Yes | No | No |
| Flat-rate pricing | Yes | No (per-node) | No ($10K+/yr) |
| Self-hosted / air-gapped | Yes | Yes | No |
Ready to see your compliance score?
[Install Free — takes 60 seconds] or [Talk to us about a SOC2 Assessment]
This is the highest-intent page on the site. The CLI upgrade prompt links directly here (varax.io/pricing).
| Free | Pro ($149/month) | |
|---|---|---|
| Compliance scanning | All checks | All checks |
| CLI output | Summary only | Full detailed output |
| PDF reports | No | Audit-ready |
| SOC2 control mapping | Basic | Complete with evidence |
| Auto-remediation | Dry-run only | Full auto-fix |
| Email support | Community only | Priority email |
| License | Apache 2.0 | Commercial |
- Toggle between monthly / annual pricing (annual = 2 months free)
- "View Sample Report" link next to Pro tier
- FAQ section addressing common objections
- Money-back guarantee badge (30-day)
- Stripe Checkout integration
Purpose: Show, don't tell. The sample report is the single most persuasive asset for converting free users to Pro.
- Interactive HTML version of a Varax compliance report
- Generated from a real Kind cluster with intentional failures
- Downloadable PDF version
- Comparison callout: "Free tier shows a summary. Pro generates this full report."
Split into two clear sections:
Varax Compliance Docs (/docs/compliance/):
- Quickstart (5-minute install)
- Configuration (ComplianceConfig CRD reference)
- Scanning (scanner details, check list)
- Reports (types, generation)
- Remediation (auto-fix guide)
- SOC2 Mapping (full control reference)
- FAQ
Varax Monitor Docs (/docs/monitor/):
- Quickstart (60-second install)
- Metrics (Prometheus reference)
- Dashboards (Grafana setup)
- Alerts (alert rules reference)
- FAQ
Purpose: Sell the $2K-$5K SOC2 Readiness Assessment service.
- What the engagement includes (install, scan, manual review, written recommendations, walkthrough call, 30-day follow-up)
- Pricing: "Starting at $2,000"
- Who it's for: "Teams that want hands-on help getting SOC2-ready"
- What you get: Deliverables list
- CTA: "Schedule a call" (Calendly embed or link)
- Testimonials (once available)
- Founder story: Why you built this (Kubernetes expertise + compliance pain point)
- Open-source commitment: Why the core is Apache 2.0
- Mission: Make Kubernetes compliance accessible to every team
- Link to Varax Monitor as proof of community commitment
- Photo optional but adds trust for consulting sales
This is a full product page — not a sidebar mention. Varax Monitor is the first thing many users will encounter from the Varax brand, so it needs to stand on its own while naturally leading visitors toward the broader ecosystem.
Varax Monitor
Free Kubernetes CronJob monitoring. Zero config. Zero cost.
Auto-discover every CronJob in your cluster. Track execution, detect failures,
alert on missed schedules — all through Prometheus and Grafana. Installs in 60 seconds.
[Install Now] [View on GitHub]
The problem: Kubernetes CronJobs fail silently. Your nightly backup didn't run? Your report generator has been broken for a week? You won't know until someone complains. Existing solutions are either expensive SaaS tools that require per-job configuration, or hours of DIY Prometheus PromQL wrangling.
The solution: One Helm command. Zero configuration. Every CronJob monitored automatically.
- Auto-Discovery — Detects every CronJob in your cluster automatically using Kubernetes Informers. Add a new CronJob? It's monitored instantly.
- Pre-Built Dashboards — Import the included Grafana dashboard and see all your CronJobs in one view. Execution history, success rates, duration trends.
- Smart Alert Rules — Pre-configured Prometheus alerts for: job failures, missed schedules, abnormal duration, and stuck jobs. Copy-paste into your AlertManager.
- Prometheus Native — Exports clean, well-labeled Prometheus metrics. Works with your existing monitoring stack. No new tools to learn.
- Lightweight — <50MB memory, <0.05 CPU. Read-only cluster access. No persistent storage needed.
- 100% Free — Apache 2.0 licensed. No per-job pricing. No telemetry. No vendor lock-in.
Quick-reference table on the landing page. Links to full docs for details.
| Metric | Type | Description |
|---|---|---|
cronjob_last_execution_status |
Gauge | Last execution result (1=success, 0=failure) |
cronjob_last_execution_duration_seconds |
Gauge | Duration of last execution |
cronjob_execution_total |
Counter | Total executions (labeled success/failure) |
cronjob_missed_schedules_total |
Counter | Missed schedule count |
cronjob_next_schedule_time |
Gauge | Unix timestamp of next expected run |
cronjob_is_suspended |
Gauge | Whether the CronJob is suspended |
[GitHub stars] [Docker pulls] [Clusters monitored] [CronJobs tracked]
Early stage fallback: "Trusted by Kubernetes operators running production clusters on EKS, AKS, and GKE."
This should feel natural, not like an upsell popup. Frame it as "more from the same team":
Your CronJobs are monitored. But is your cluster compliant?
Varax scans your Kubernetes cluster for SOC2 violations
and generates audit-ready reports with one CLI command.
Same Kubernetes-native approach. Same zero-config philosophy.
[Learn about Varax Compliance] [View Sample Report]
Design note: This cross-promotion block should be visually distinct (different background, subtle border) but not aggressive. Think of how Vercel promotes Next.js on their other product pages — present but tasteful. No popups, no modals, no "Don't miss this!" energy.
Monitor every CronJob in your cluster. Free forever.
$ helm install varax-monitor varax/varax-monitor
[Install Now] [Read the Docs] [Star on GitHub]
Separate documentation section within the shared docs hub. Same design, same search index, but clearly scoped.
Quickstart (/docs/monitor/quickstart)
- Prerequisites (Helm, kubectl, a Kubernetes cluster with Prometheus)
- Installation (2 commands)
- Verifying it's working (check metrics endpoint)
- Importing the Grafana dashboard
- Setting up alerts
Metrics Reference (/docs/monitor/metrics)
- Complete list of all exported metrics
- Label descriptions
- Example PromQL queries for common use cases
Dashboards (/docs/monitor/dashboards)
- Grafana dashboard JSON import instructions
- Dashboard panel descriptions
- Customization guide
Alert Rules (/docs/monitor/alerts)
- Pre-built alert rules with AlertManager configuration
- Tuning thresholds for your environment
- Slack/PagerDuty/email integration examples
FAQ (/docs/monitor/faq)
- "Does it work with kube-state-metrics?" — Yes, it complements it.
- "What K8s versions are supported?" — 1.21+
- "Can I monitor specific namespaces only?" — Yes, via Helm values.
- "How much resources does it use?" — <50MB RAM, <0.05 CPU.
The Varax Monitor expands the content marketing surface area significantly. These posts target a broader K8s operations audience that may not be searching for compliance content yet:
| # | Title | Target Keyword | Cross-Sell Potential |
|---|---|---|---|
| 1 | "Monitor All Your Kubernetes CronJobs in 60 Seconds" | kubernetes cronjob monitoring | Low (awareness) |
| 2 | "Why Your Kubernetes CronJobs Are Failing Silently" | kubernetes cronjob failing | Low (awareness) |
| 3 | "Prometheus Metrics for Kubernetes CronJobs: A Complete Guide" | prometheus cronjob metrics | Medium (technical audience) |
| 4 | "Kubernetes CronJob Alerting with Prometheus and AlertManager" | kubernetes cronjob alerts | Medium (technical audience) |
| 5 | "CronJob Monitoring + SOC2 Compliance: Your K8s Operations Checklist" | kubernetes operations checklist | High (bridge content) |
| 6 | "From CronJob Monitoring to Full Cluster Compliance with Varax" | (branded) | High (conversion content) |
Posts #5 and #6 are bridge content — they naturally connect the Varax Monitor audience to the compliance platform by framing them as two parts of a mature Kubernetes operations practice.
GitHub README "Learn more" link
→ varax.io
→ Docs/Quickstart
→ Install free tier
→ Run `varax report`
→ See upgrade prompt in CLI
→ varax.io/pricing
→ Stripe Checkout
→ Pro customer
Key metric: GitHub referral → Install conversion rate
This is the signature funnel for the two-product strategy:
Search "kubernetes cronjob monitoring" or Reddit/HN discovery
→ varax.io/monitor (or GitHub README)
→ Install Varax Monitor (free)
→ Positive experience, trust established
→ See cross-promotion in CLI output, docs, or website
→ Visit varax.io/sample-report or homepage
→ Learn about Varax compliance platform
→ Install compliance free tier
→ Upgrade to Pro
Key metric: Varax Monitor install → Varax compliance install rate (target: 5-10%)
This funnel may take weeks or months to convert. The email nurture sequence bridges the gap — Varax Monitor users who sign up for the newsletter receive compliance-related content that surfaces the paid product naturally.
Google search "SOC2 Kubernetes compliance"
→ Blog post on varax.io/blog
→ Email signup (in-content CTA or exit intent)
→ Nurture sequence (3-5 emails)
→ Install free tier
→ Upgrade to Pro
Key metric: Blog visit → Email signup rate (target: 3-5%)
CLI upgrade prompt → varax.io/pricing
→ View sample report
→ Stripe Checkout
→ Pro customer
Key metric: Pricing page → Purchase conversion rate (target: 5-10%)
Homepage or blog → varax.io/consulting
→ Schedule call (Calendly)
→ Discovery call
→ SOC2 Assessment engagement ($2K-$5K)
→ Pro subscriber post-engagement
Content marketing is the primary growth engine. The blog targets high-intent keywords that DevOps engineers and CTOs search when they're facing compliance deadlines.
- SOC2 for Kubernetes — The primary pillar. Everything about achieving and maintaining SOC2 in K8s environments.
- Kubernetes Security Hardening — CIS Benchmarks, NSA/CISA guidelines, pod security, RBAC best practices.
- Compliance Automation — General compliance engineering, evidence collection, audit preparation.
- Kubernetes Operations — CronJob monitoring, observability, production best practices (feeds the Varax Monitor audience).
| # | Title | Target Keyword | Funnel |
|---|---|---|---|
| 1 | "The Complete Guide to SOC2 Compliance for Kubernetes" | kubernetes soc2 | SEO → Email |
| 2 | "CIS Kubernetes Benchmark: What It Is and How to Automate It" | cis benchmark kubernetes | SEO → Email |
| 3 | "Automating SOC2 Evidence Collection in Kubernetes" | soc2 automation | SEO → Install |
| 4 | "Kubernetes RBAC Audit: Finding Permission Gaps Before Your Auditor Does" | kubernetes rbac audit | SEO → Email |
| 5 | "Why We Built Varax: The Open-Source Kubernetes Compliance Tool" | (branded) | Trust building |
Each post should include:
- Title + meta description (SEO optimized)
- Author name and date
- Estimated reading time
- Table of contents for posts >1,500 words
- Code blocks where relevant
- CTA at the bottom (relevant to the post topic)
- Related posts section
- Social sharing links
| Keyword | Monthly Volume (Est.) | Difficulty | Page Target |
|---|---|---|---|
| kubernetes soc2 | 200-500 | Medium | Blog + Homepage |
| kubernetes compliance | 500-1,000 | Medium-High | Blog + Homepage |
| kubernetes security audit | 200-400 | Medium | Blog |
| cis benchmark kubernetes | 500-800 | Medium | Blog + Docs |
| kubernetes compliance automation | 100-200 | Low-Medium | Homepage |
| Keyword | Monthly Volume (Est.) | Page Target |
|---|---|---|
| kubernetes audit logging | 300-500 | Blog |
| soc2 automation tools | 500-1,000 | Blog |
| kubernetes rbac audit | 200-400 | Blog |
| kubernetes network policy soc2 | 50-100 | Blog |
| kubernetes security hardening | 300-500 | Blog |
- Server-side rendering or static generation (Astro SSG or Next.js SSR)
- Proper meta tags, Open Graph, and Twitter cards on every page
- Sitemap.xml and robots.txt
- Structured data (Organization, SoftwareApplication, Article schemas)
- Canonical URLs
- Fast load times (<2s LCP) — critical for developer audience
- Mobile responsive (engineers read on phones at conferences)
- Submit to CNCF Landscape / Artifact Hub (backlink + discovery)
- GitHub README links back to varax.io
- Blog posts shared on Reddit, Hacker News, Kubernetes Slack
- Guest posts on DevOps blogs (optional, lower priority)
- Conference talk slides linking to Varax
| Component | Technology | Rationale |
|---|---|---|
| Framework | Astro or Next.js (static export) | Fast static sites, great DX, MDX support for blog |
| Styling | Tailwind CSS | Consistent with the product ecosystem, fast to iterate |
| Blog/Docs | MDX (Markdown + components) | Write content in Markdown, embed interactive elements |
| Search (Docs) | Algolia DocSearch (free for OSS) | Industry standard for dev docs search |
| Hosting | Cloudflare Pages or Vercel | Free tier sufficient, global CDN, automatic SSL |
| CMS | Git-based (MDX files in repo) | No external CMS needed — content lives in the repo |
| Analytics | Plausible or Fathom | Privacy-respecting, no cookie banner needed |
| Buttondown or ConvertKit | Simple, developer-friendly email marketing | |
| Payments | Stripe Checkout | Already specified in the Varax Compliance PRD |
| Forms | Calendly (consulting) | Scheduling for consulting calls |
- The marketing site is primarily static content (blog, docs, landing pages)
- Astro ships zero JS by default, resulting in faster page loads
- Astro supports MDX natively for blog and docs
- Interactive islands (pricing toggle, search) can use React components where needed
- Astro + Cloudflare Pages = effectively free hosting with global CDN
Note: This is separate from the v2 SaaS dashboard, which will use Next.js. The marketing site and the product dashboard are different codebases.
varax-website/
├── src/
│ ├── pages/
│ │ ├── index.astro # Homepage
│ │ ├── pricing.astro # Pricing page
│ │ ├── monitor.astro # Varax Monitor product page
│ │ ├── sample-report.astro # Sample report page
│ │ ├── consulting.astro # Consulting page
│ │ ├── about.astro # About page
│ │ ├── changelog.astro # Changelog
│ │ ├── privacy.astro # Privacy policy
│ │ ├── terms.astro # Terms of service
│ │ ├── blog/
│ │ │ ├── index.astro # Blog listing
│ │ │ └── [...slug].astro # Dynamic blog post pages
│ │ └── docs/
│ │ ├── index.astro # Docs hub
│ │ └── [...slug].astro # Dynamic doc pages
│ ├── content/
│ │ ├── blog/ # MDX blog posts
│ │ └── docs/
│ │ ├── compliance/ # Varax compliance docs (MDX)
│ │ └── monitor/ # Varax Monitor docs (MDX)
│ ├── components/
│ │ ├── Header.astro
│ │ ├── Footer.astro
│ │ ├── ProductCard.astro
│ │ ├── PricingCard.astro
│ │ ├── ComparisonTable.astro
│ │ ├── CodeBlock.astro
│ │ ├── TerminalDemo.astro
│ │ ├── NewsletterSignup.astro
│ │ ├── CrossPromo.astro
│ │ └── SampleReport.astro
│ ├── layouts/
│ │ ├── Base.astro
│ │ ├── Blog.astro
│ │ └── Docs.astro
│ └── styles/
│ └── global.css
├── public/
│ ├── reports/
│ ├── dashboards/
│ ├── og-images/
│ └── favicon.svg
├── astro.config.mjs
├── tailwind.config.mjs
└── package.json
Inspiration: Tailscale, Linear, Planetscale — clean developer tool marketing sites with technical depth.
NOT: Enterprise SaaS landing pages with stock photos, gradient blobs, and "Schedule a Demo" popups.
- Dark mode first — the primary audience lives in dark terminals. Offer light mode toggle.
- Monospace code — all code blocks, terminal output, and CLI examples in a clear monospace font (JetBrains Mono or similar).
- Minimal animation — subtle transitions only. No parallax, no auto-playing videos, no scroll-jacking.
- Terminal-inspired hero — the hero visual should feel like a terminal window showing
varax scanin action. - High information density — DevOps engineers want facts, not whitespace. Pack more content per screen than a typical SaaS site.
- No stock photos — use diagrams, terminal screenshots, report screenshots, and code. If people imagery is needed, use illustrations.
- Color palette — derive from the Kubernetes blue (#326CE5) ecosystem. Consider a complementary security-oriented accent (green for "passing" checks, red/amber for failures).
- Typography — clean sans-serif for body (Inter, system font stack), monospace for code. Two font families maximum.
- Blog post in-content CTAs ("Get the full SOC2 checklist")
- Newsletter signup in footer
- Varax Monitor docs ("Stay updated on new features")
- Exit intent on high-value pages (pricing, sample report)
Sequence A: Compliance-focused (entered via blog or homepage)
- Welcome + "The 5-Minute SOC2 Readiness Check for Kubernetes" (immediate value)
- "How Varax Automates SOC2 Evidence Collection" (product education)
- "Case Study: From 0 to SOC2-Ready in 30 Days" (social proof, when available)
- "Free vs Pro: What You Get with a Varax License" (conversion)
Sequence B: Varax Monitor-focused (entered via monitor docs or GitHub)
- Welcome + "3 Prometheus Queries Every K8s Operator Should Know" (immediate value)
- "Why CronJob Monitoring Is Just the Start of K8s Observability" (bridge)
- "From Monitoring to Compliance: The K8s Maturity Path" (introduce Varax compliance)
- "Try Varax Free: See Your Cluster's Compliance Score" (conversion)
- User clicks "Buy Pro" on pricing page
- Stripe Checkout session created (server-side)
- User completes payment on Stripe-hosted page
- Stripe webhook triggers license key generation
- User receives email with license key and activation instructions
- User runs
varax activate [LICENSE_KEY]in their cluster
- Product: "Varax Pro"
- Price: $149/month or $1,490/year (2 months free)
- Payment methods: Credit card (Stripe default)
- Receipts: Automatic via Stripe
- Refund policy: 30-day money-back guarantee
- Plausible or Fathom — privacy-respecting, no cookie banner needed
- Stripe Dashboard — payment analytics
- Google Search Console — SEO performance
- Homepage → Pricing page navigation
- Pricing page → Stripe Checkout initiated
- Blog post → Email signup
- Varax Monitor page → Compliance page navigation (cross-sell)
- Docs quickstart → Install command copied
- Sample report page → Pricing page navigation
- What data is collected (analytics only — no PII unless they purchase)
- Email list data handling
- Stripe payment data (Stripe handles PCI compliance)
- Cookie policy (none if using Plausible/Fathom)
- GDPR compliance statement
- License terms for Varax free tier (Apache 2.0)
- License terms for Varax Pro (commercial license)
- Acceptable use
- Payment terms and refund policy (30-day money-back guarantee)
- Limitation of liability
- Governing law
Recommendation: Use a template generator for initial drafts (e.g., Termly, iubenda) and have a lawyer review before launch. Budget: $500-$1,000 for legal review.
Goal: Start building SEO authority and email list before the product ships.
- Register domain (varax.io secured)
- Deploy a minimal coming-soon page with email capture
- Publish 2-3 foundational blog posts (target primary SEO keywords)
- Set up analytics
- Create social media accounts
Deliverables: varax.io live, 1-3 blog posts indexed, email capture working.
Goal: Minimum viable site for the Varax Monitor launch. This is Varax's first public appearance.
Pages to ship:
- Homepage (two-product hero, features, install CTAs)
- Varax Monitor landing page (
/monitor) - Varax Monitor quickstart docs
- Blog with 2-3 CronJob-focused posts
- Privacy policy and terms of service
- About page
Not needed for Phase 1: Pricing page, Stripe integration, compliance docs, sample report, consulting page.
Timeline: 1 week of focused development (Varax Monitor ships in Weeks 1-3, so the site needs to be ready).
Goal: Full marketing site for the Varax compliance platform launch.
Pages to add:
- Pricing page with Stripe Checkout integration
- Varax compliance quickstart docs
- Sample report page
- Full compliance documentation
- 3-5 compliance-focused blog posts
Timeline: 1-2 weeks of focused development.
Goal: Full content marketing engine running.
- Complete documentation site (all doc pages)
- Consulting page
- 10+ blog posts published
- Email nurture sequence active
- Comparison table on homepage
- Changelog page
Goal: Conversion optimization based on data.
- A/B test pricing page layout
- Add ROI calculator
- Add customer testimonials / case studies (once available)
- Optimize based on analytics data
- Consider adding a product demo video (terminal screencast)
Product name and domain— Resolved. Brand is Varax, domain is varax.io, compliance platform is Varax, OSS monitor is Varax Monitor.- Blog authoring workflow — Write in Markdown and commit to Git? Or use a headless CMS? Recommendation: Git-based (simpler, no dependencies).
- Docs versioning — Do we need versioned docs from day one, or can we start with "latest only" and add versioning later? Recommendation: Latest-only for v1.
- Sample report: real or synthetic data? — The sample report should show realistic cluster data. Do we generate this from a sample Kind cluster, or hand-craft the data? Recommendation: Generate from a real Kind cluster with intentional failures for demonstration.
- Consulting scheduling — Calendly free tier, or build a simple contact form? Recommendation: Calendly free tier (less friction, immediate confirmation).
- Legal budget — Do we want a lawyer to review privacy policy and ToS before launch, or use templates for MVP? Recommendation: Templates for MVP, lawyer review within 60 days.
- GitHub org availability — Need to confirm
github.com/varaxis available. If not, usegithub.com/varax-io.
Document Version: 2.0 Last Updated: March 2026 Status: Planning Brand: Varax Domain: varax.io