Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as opaque submodule gitlinks on GitHub) into fully-tracked first-party content. AITM now merges its 7 vendored repos as first-party engines: - memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts - git: vendored C git (bundled binary) + gitnexus (in-process code intelligence) - agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess) Includes the full session's product build: Gitgram web/mobile/backend features, AITM website/CLI/MCP, the unified memory layer, engine build tooling (scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md), and extensive test suites. Build artifacts, node_modules, external/, and gemini-cli are gitignored. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
56 lines
1.8 KiB
Plaintext
56 lines
1.8 KiB
Plaintext
---
|
|
title: Infrastructure Security
|
|
sidebarTitle: Infrastructure
|
|
---
|
|
|
|
The operational and platform-level protections behind Context7, including hosted infrastructure, abuse prevention, and secure development practices.
|
|
|
|
## Platform Infrastructure
|
|
|
|
### SOC 2 Compliance
|
|
|
|
Context7 runs on **SOC 2 compliant infrastructure** provided by Upstash.
|
|
|
|
- Type II SOC 2 certified infrastructure
|
|
- Regular security audits and assessments
|
|
- Continuous monitoring and compliance checks
|
|
- Industry-standard security controls
|
|
|
|
### Managed by Upstash
|
|
|
|
Context7's infrastructure is managed by the experienced Upstash team:
|
|
|
|
- 24/7 infrastructure monitoring
|
|
- Automated security patching
|
|
- DDoS protection and mitigation
|
|
- Redundant backups and disaster recovery
|
|
- Enterprise-grade reliability and uptime
|
|
|
|
### Upstash Security Practices
|
|
|
|
All security practices and certificates of Upstash apply to Context7 products:
|
|
|
|
- **Data Encryption**: Encryption at rest and in transit (TLS 1.2+)
|
|
- **Network Security**: VPC isolation, firewall rules, and network segmentation
|
|
- **Access Control**: Role-based access control (RBAC) and least privilege principles
|
|
- **Audit Logging**: Comprehensive logging of all system activities
|
|
- **Incident Response**: Documented incident response procedures
|
|
- **Vulnerability Management**: Regular security scanning and penetration testing
|
|
|
|
|
|
## Rate Limiting and Abuse Prevention
|
|
|
|
- IP-based rate limiting for anonymous requests
|
|
- API key-based rate limiting with tiered limits
|
|
- Automatic detection and blocking of abusive patterns
|
|
- Protection against DDoS and scraping attacks
|
|
|
|
## Secure Development Practices
|
|
|
|
- Regular security code reviews
|
|
- Automated dependency scanning
|
|
- Secure CI/CD pipelines
|
|
- Principle of least privilege for all systems
|
|
- Security testing in development lifecycle
|
|
|