| # PAX-Coder Contact & Provisioning
|
|
|
| **Provisioning requests are reviewed within 1–3 business days.**
|
|
|
| ---
|
|
|
| ## Quick Links
|
|
|
| | Need | Contact |
|
| |------|---------|
|
| | **Provisioning Request** | Fill form below or email jessica@collectivekitty.com |
|
| | **Pricing Questions** | See [PRICING.md](PRICING.md) |
|
| | **Technical Support** | jessica@collectivekitty.com |
|
| | **Enterprise** | jessica@collectivekitty.com |
|
| | **General Inquiry** | jessica@collectivekitty.com |
|
|
|
| ---
|
|
|
| ## Provisioning Request Form
|
|
|
| Submit a node provisioning request using this information:
|
|
|
| ### Basic Information
|
|
|
| ```
|
| Full Name (or Organization Name): ___________________
|
| Email Address: ___________________
|
| Phone (optional): ___________________
|
| Country/Region: ___________________
|
| ```
|
|
|
| ### Project / Organization
|
|
|
| ```
|
| Organization Type:
|
| [ ] Individual / Solo Developer
|
| [ ] Startup / Small Business
|
| [ ] University / Research Institution
|
| [ ] Enterprise / Large Organization
|
| [ ] Government / Defense
|
| [ ] Other: ___________________
|
|
|
| Organization Name (if applicable): ___________________
|
| Your Role / Title: ___________________
|
| ```
|
|
|
| ### Use Case
|
|
|
| ```
|
| What will you use PAX-Coder for?
|
|
|
| [ ] Research / Academic
|
| [ ] Commercial Kernel Development
|
| [ ] Production GPU Deployment
|
| [ ] Internal Tools / Private Use
|
| [ ] Evaluation / Trial
|
| [ ] Other: ___________________
|
|
|
| Describe your use case (100–500 words):
|
| ___________________________________________________________
|
| ___________________________________________________________
|
| ___________________________________________________________
|
| ```
|
|
|
| ### Technical Requirements
|
|
|
| ```
|
| Deployment Environment:
|
| [ ] Local Workstation
|
| [ ] Cloud (AWS / Azure / GCP)
|
| [ ] On-Premises Datacenter
|
| [ ] Hybrid
|
| [ ] Other: ___________________
|
|
|
| GPU Hardware:
|
| [ ] NVIDIA RTX (sm_86): RTX 3080, 4090, etc.
|
| [ ] NVIDIA A/H100 (sm_90)
|
| [ ] Other: ___________________
|
|
|
| Estimated Kernel Volume:
|
| [ ] 1–10 kernels/year
|
| [ ] 10–50 kernels/year
|
| [ ] 50–200 kernels/year
|
| [ ] 200+ kernels/year
|
| [ ] Unknown / TBD
|
|
|
| Team Size:
|
| [ ] Solo
|
| [ ] 2–5 people
|
| [ ] 5–20 people
|
| [ ] 20+ people
|
| ```
|
|
|
| ### Plan Selection
|
|
|
| ```
|
| Which tier are you interested in?
|
|
|
| [ ] Individual / Node Key ($250–$500)
|
| [ ] Commercial Team ($12,000–$25,000/year)
|
| [ ] Enterprise Verification ($50,000+/year)
|
| [ ] Proof Audit & Sign-Off ($10,000+/kernel)
|
| [ ] Not sure / Need consultation
|
| ```
|
|
|
| ### Additional Information
|
|
|
| ```
|
| How did you hear about PAX-Coder?
|
| [ ] GitHub
|
| [ ] Academic Paper
|
| [ ] Referral
|
| [ ] Search Engine
|
| [ ] Conference / Event
|
| [ ] Other: ___________________
|
|
|
| Do you have specific requirements or questions?
|
| ___________________________________________________________
|
| ___________________________________________________________
|
| ```
|
|
|
| ---
|
|
|
| ## Submission
|
|
|
| ### Online Form
|
|
|
| Visit: https://snapkittywest.com/pax-coder/request
|
|
|
| (Form auto-generates provisioning request ticket)
|
|
|
| ### Email
|
|
|
| Send to: **jessica@collectivekitty.com**
|
|
|
| Subject: `Provisioning Request: [Your Name/Organization]`
|
|
|
| Include all information from the form above.
|
|
|
| ### Response
|
|
|
| - **Individual tier:** 1–3 business days
|
| - **Commercial/Enterprise:** 2–5 business days (may include business development call)
|
|
|
| ---
|
|
|
| ## Provisioning Process Timeline
|
|
|
| ### Step 1: Request Submitted
|
| - Form / email received
|
| - Ticket created (you receive ticket number)
|
|
|
| ### Step 2: Review (1–3 business days)
|
| - Qualification assessment
|
| - Use case review
|
| - Technical requirements check
|
|
|
| ### Step 3: Approval / Rejection
|
| - Approved: Proceed to Step 4
|
| - Rejected: Contact with explanation and alternative options
|
| - On Hold: Request for additional information
|
|
|
| ### Step 4: Commercial Agreement & Payment
|
| - Individual: Secure payment link sent
|
| - Commercial/Enterprise: Legal review and formal agreement
|
|
|
| ### Step 5: Payment Processing
|
| - Individual: Credit card / PayPal / Wire (1–3 days)
|
| - Commercial/Enterprise: PO / Invoice / Custom terms
|
|
|
| ### Step 6: Node Provisioning
|
| - Node credential created
|
| - Operator-signed authorization issued
|
| - Authentication material provided
|
| - Activation instructions sent
|
|
|
| ### Step 7: Activation
|
| - Configure credential in your environment
|
| - Begin using PAX-Coder with production authorization
|
|
|
| **Total time: 3–14 business days (depending on tier)**
|
|
|
| ---
|
|
|
| ## Credential Delivery
|
|
|
| After approval and payment:
|
|
|
| ### Individual Tier
|
|
|
| You receive:
|
| - `node.json` — Node identity metadata
|
| - `node_pk.pem` — Public key (for verification)
|
| - Authentication token (for your environment)
|
| - Quick-start guide
|
|
|
| Delivery method:
|
| - Secure email with encrypted attachment
|
| - Alternative: Secure download link
|
|
|
| ### Commercial/Enterprise Tier
|
|
|
| You receive:
|
| - Formal credential package
|
| - Multiple node keys (if multiple environments)
|
| - Administrative documentation
|
| - Deployment guide
|
| - Direct contact information
|
|
|
| Delivery method:
|
| - Secure delivery + executive briefing call
|
| - Optional: On-site activation support
|
|
|
| ---
|
|
|
| ## Your Provisioned Node
|
|
|
| Once provisioned, your node:
|
|
|
| ✅ **Can:**
|
| - Sign releases using `sovereign/generate_release.sh`
|
| - Request authorization capabilities
|
| - Perform protected kernel operations
|
| - Deploy to production
|
| - Use commercial licensing
|
|
|
| ❌ **Cannot (by design):**
|
| - Generate fake authorization locally
|
| - Create unauthorized capabilities
|
| - Bypass the authorization gate
|
| - Deploy with another organization's node
|
| - Transfer to another organization
|
|
|
| ---
|
|
|
| ## Renewal & Management
|
|
|
| ### Individual Tier (One-Time)
|
|
|
| - No renewal required
|
| - Credential remains active indefinitely
|
| - Contact support if you need additional nodes
|
|
|
| ### Commercial/Enterprise Tier (Annual)
|
|
|
| Renewal notice: 60 days before contract end
|
| - Email renewal option
|
| - Pricing adjustment (if applicable)
|
| - New agreement (if terms change)
|
|
|
| To renew:
|
| - Reply to renewal notice, OR
|
| - Contact: jessica@collectivekitty.com
|
|
|
| ---
|
|
|
| ## Revocation & Termination
|
|
|
| ### Standard Termination
|
|
|
| - Commercial/Enterprise: Subscription expires on renewal date
|
| - Active nodes become inactive
|
| - New capabilities not issued
|
| - Reactivation available anytime
|
|
|
| ### Early Termination
|
|
|
| Contact: jessica@collectivekitty.com
|
|
|
| - Prorated refunds available (Individual tier: within 30 days)
|
| - Commercial/Enterprise: Per contract terms
|
|
|
| ### Terms Violation
|
|
|
| Violations may result in:
|
| - Immediate node revocation
|
| - No refund
|
| - Possible legal action
|
|
|
| Examples:
|
| - Unauthorized redistribution
|
| - Sharing credentials with other organizations
|
| - Use outside provisioning agreement scope
|
| - Unauthorized production deployment
|
|
|
| ---
|
|
|
| ## FAQ
|
|
|
| **Q: How long does provisioning take?**
|
|
|
| A: 3–14 business days total, depending on tier and complexity.
|
|
|
| **Q: Can I get a trial?**
|
|
|
| A: Public clone is a free trial. You can verify integrity, examine source, and test locally. Contact for time-limited trial credentials on Commercial tiers.
|
|
|
| **Q: What if I'm from a sanctioned country?**
|
|
|
| A: Contact support; we comply with US export regulations.
|
|
|
| **Q: Can I get a partial refund?**
|
|
|
| A: Individual tier: 30-day money-back guarantee (within 30 days). Commercial/Enterprise: Per contract terms.
|
|
|
| **Q: What payment methods do you accept?**
|
|
|
| A:
|
| - Individual: Credit card, PayPal, Wire transfer
|
| - Commercial/Enterprise: PO, Invoice, Wire, Custom
|
|
|
| **Q: Can I upgrade/downgrade my plan?**
|
|
|
| A: Yes. Contact support to discuss plan changes.
|
|
|
| **Q: Do you offer volume discounts?**
|
|
|
| A: Contact jessica@collectivekitty.com for volume/multi-year pricing.
|
|
|
| ---
|
|
|
| ## Support During Provisioning
|
|
|
| Have questions during provisioning?
|
|
|
| **Email:** jessica@collectivekitty.com
|
| **Response time:** 1 business day
|
|
|
| Please include:
|
| - Your provisioning request ticket number (if you have it)
|
| - Your question
|
| - Any relevant context
|
|
|
| ---
|
|
|
| ## Next Steps
|
|
|
| 1. **Review [PRICING.md](PRICING.md)** to understand tiers
|
| 2. **Review [LICENSE.md](LICENSE.md)** for commercial licensing terms
|
| 3. **Complete this provisioning form** (above)
|
| 4. **Submit** via online form or email
|
| 5. **Wait for response** (1–3 business days)
|
| 6. **Receive node credential** after approval
|
| 7. **Begin using PAX-Coder** in production
|
|
|
| ---
|
|
|
| **Questions?**
|
| Email: jessica@collectivekitty.com
|
|
|
| **Ready to request?**
|
| Form: https://snapkittywest.com/pax-coder/request
|
|
|
| ---
|
|
|
| **PAX-Coder is developed by SnapKitty.**
|
| **© 2026 SnapKitty. All rights reserved.**
|
|
|
