Small team: Teams plan
Plan at a Glance
Price
$45 per month
Credits
28,000 per month
Best for
Small teams and growing organizations that need shared context, collaboration, and centralized management
Key differentiator
Collective Memory with three-layer architecture
Includes everything in Pro
Yes
What’s Included
The Teams Plan is built for collaboration. It takes everything in the Pro Plan and adds the features that make Skynet’s value compound across a group. One person builds a skill, the entire team benefits. Knowledge stays in the organization, not in individual inboxes.
You get:
- 28,000 credits per month
- Full model library with Smart Routing and Manual Pinning
- Shared team workspace with Collective Memory
- Role-based access and project sharing
- Centralized billing and usage management
- Skills, Projects, and Connectors
- Priority processing and higher rate limits
The Teams Plan is where Skynet stops being a personal tool and becomes organizational infrastructure.
Credits and Usage
You receive 28,000 credits per month. Credits are consumed when you:
- Run an agent
- Call a language model
- Process a document
- Execute a skill or connector
Frontier models like GPT-4o and Claude 3 Opus consume more credits per task. Lightweight models like GPT-4o mini and Claude 3.5 Haiku consume fewer. Smart Routing helps optimize credit usage by routing simple tasks to lightweight models and reserving frontier models for complex work.
With 28,000 credits, a team of 3 to 5 people can run daily automations, model calls, and document processing without hitting limits in a typical work month. Heavy usage teams may want to monitor consumption through the centralized usage dashboard.
Credits do not roll over. They reset at the start of each billing cycle.
Collective Memory
Collective Memory is the feature that separates Skynet from every other AI platform. It is a living organizational layer where individual knowledge rolls up into team knowledge, and team knowledge rolls up into a single company brain.
No manual uploads are needed. The system learns from the natural flow of work across meetings, chats, emails, and connected tools. The workspace gets smarter every day without anyone doing anything differently.
Three-Layer Memory Architecture
Individual Memory
The personal layer. Private by default. Adapts to how each person works. Your preferences, your patterns, your context. No one else sees this unless you choose to share it.
Team Memory
The shared context layer for a specific team or project. This is where collaboration happens. When someone joins a project, they inherit the full context. Onboarding gets faster because the new person does not start from zero. The team's accumulated knowledge is already there.
Company Brain
The top layer. The cumulative context of the entire organization. This is where organizational intelligence lives. Knowledge flows upward through the hierarchy. What one team learns can benefit the entire company, subject to access controls.
How Knowledge Flows
Knowledge moves upward through the hierarchy. Individual insights become team context. Team context feeds the company brain. At each layer, access controls determine what is shared and what stays private.
The workspace gets smarter over time instead of resetting to zero. Every meeting, every chat, every email processed through a connector adds to the collective context. This is what makes Skynet different from a chat tool that forgets everything when you close the tab.
Memory Segregation
Collective Memory is not a single shared bucket. Department-specific data stays separate by default. A Finance project does not bleed into a Design project unless explicitly shared. This keeps context relevant and clean. Access controls ensure that sensitive information stays where it belongs.
Projects
A Project is a shared container for collaborative work. It groups collective memory, skills, and agents around a specific workstream. Available on Teams and Enterprise plans.
How Projects Work
Everything inside a project stays connected. Conversations, automations, and accumulated knowledge all live in the same space. When someone joins a project, they inherit the full context. When an agent runs inside it, it draws from the project’s memory and skills.
The workspace gets smarter over time instead of resetting to zero. This solves one of the biggest problems in modern work: context loss between tools, people, and sessions.
Collective Memory Inside Projects
Every project carries its own collective memory. This is shared context that stays within the team or organization. It builds automatically as the team interacts through meetings, chats, emails, and connected tools.
Projects mirror your organizational structure. Department-specific data stays separate by default. A Finance project does not bleed into a Design project unless explicitly shared. This keeps context relevant and clean.
Parallel Sub-Agent Orchestration
Projects support parallel sub-agent orchestration with skill chaining. This is a core architectural difference between Skynet and sequential tools like Claude. Instead of processing one task at a time, Skynet forks parallel sub-agents that can run thousands of tasks simultaneously.
Each sub-agent specializes in a specific domain. The skill chain passes filtered, relevant context between agents. This is where the 300x data reduction comes in. For example, when processing 1,000 LinkedIn profiles, Skynet filters to only the relevant fields before passing data to the main model. The result is crystal clear output without hallucination, at a fraction of the cost and context usage.
Skills
A Skill is a saved automation that performs a specific task or workflow. Skills can be triggered on a schedule, invoked on demand, or activated automatically.
How Skills Are Created
Skills are created in two ways:
Observation
The Copilot watches your work patterns and proposes a skill based on what it sees.
Instruction
You describe what you want in plain language and Skynet builds it.
No code required. This is a core differentiator. Engineers are needed for Claude. They are not needed for Skynet. Business users can build and deploy skills without technical support.
Skill Lifecycle
Every skill follows a four-stage lifecycle:
Detection
The system identifies a repeatable pattern or receives your instruction.
Proposal
A skill is proposed based on the detected pattern or your description.
Approval
A human reviews and approves the skill before it goes live. Nothing runs without human sign-off.
Execution
The skill runs on its trigger, whether scheduled, on demand, or automatic.
Team-Shared Skills
On the Teams Plan, one person builds a skill and the entire team benefits. Skills are reusable assets within the shared workspace. A skill built by one team member is available to everyone with the right permissions. This means your automation library grows with every person who contributes.
Models
The Teams Plan includes access to frontier models from every major provider through a single workspace. No separate accounts. No separate API keys. No separate billing relationships.
Smart Routing
By default, Skynet evaluates each prompt and routes it to the model best suited for the task. The system balances quality, speed, and credit cost in real time. A quick summary may go to a lightweight model. A complex reasoning task may go to a frontier model. You do not have to choose.
Manual Pinning
When you want control, you can pin a specific model to a conversation or project. Pin Claude 3 Opus for deep analysis. Switch to GPT-4o mid-thread without losing context. Your conversation history and memory carry over.
Unified Memory Across Models
When you switch from one model to another mid-conversation, your context carries over. The new model picks up where the last one left off. You do not re-explain your project or re-upload documents. The workspace owns the context, not the individual model.
Available Models
| Provider | Models |
|---|---|
| OpenAI | GPT-4o, GPT-4o mini, o1-preview, o1-mini |
| Anthropic | Claude 3.5 Sonnet, Claude 3 Opus |
| Gemini 1.5 Pro, Gemini 1.5 Flash | |
| DeepSeek | DeepSeek V3, DeepSeek R1 |
| Meta (via Groq) | Llama 3.1 70B, Llama 3.1 8B |
| Perplexity | Sonar Large, Sonar Online |
| Mistral | Mistral Large 2 |
Frontier models consume more credits. Lightweight models consume fewer. Smart Routing optimizes the balance automatically.
Connectors
Connectors are secure, read-optimized integrations that let Skynet draw from your existing tools without disrupting them.
Available Connectors
Email
Connects to your email environment for context and automation.
Calendar
Syncs scheduling data for meeting support and planning.
Chat
Integrates with your chat platform for conversation context.
Meetings
Processes meeting content for notes, summaries, and action items.
How Connectors Work
All source data remains in its native environment. Connectors are non-destructive. They read and process context without modifying your original data. Governance is enforced at the connector level, preserving existing access controls and security boundaries.
Each connector preserves contextual relationships. A meeting connected through the Meetings connector retains its link to the calendar event, the chat thread, and the email follow-up. This is how Collective Memory builds automatically without manual uploads.
Platform Security
Skynet uses TEE-based secure computing with encryption keys burnt in-chip. This means your data is processed in a trusted execution environment where the encryption keys are embedded directly in the hardware. Your data is protected at the compute layer, not just at rest or in transit. This is a core architectural advantage that applies across all plans, including Teams.
Role-Based Access and Permissions
The Teams Plan includes role-based access control. This means you can manage who sees what within your shared workspace.
Project-level permissions
Control who can view, edit, or manage specific projects.
Memory access controls
Individual Memory stays private by default. Team Memory and Company Brain access is governed by roles.
Skill permissions
Control who can create, approve, and execute skills.
Connector access
Manage which team members can connect and configure integrations.
Role-based access ensures that collaboration does not come at the cost of security. Sensitive information stays where it belongs.
Centralized Billing and Usage Management
The Teams Plan includes centralized billing and usage management. One administrator can monitor and control the entire team’s usage from a single dashboard.
Single billing relationship
One invoice for the entire team. No per-seat charges.
Usage monitoring
Track credit consumption across the team in real time.
Credit allocation visibility
See how credits are being used across projects, skills, and model calls.
User management
Add, remove, and manage team members from a central interface.
Centralized management means you never lose visibility into how your team is using Skynet. You can spot inefficiencies, reallocate resources, and keep costs under control.
What’s NOT Included
The Teams Plan covers most team needs. The following features require an upgrade to the Enterprise Plan:
| Feature | Teams | Enterprise |
|---|---|---|
| Custom credit allocation | No | Yes |
| Data residency options | No | Yes |
| Advanced governance and compliance controls | No | Yes |
| Dedicated support | No | Yes |
| Custom integrations | No | Yes |
| SSO/SAML | No | Yes |
| Audit logs | No | Yes |
| API access | No | Yes |
| White-label options | No | Yes |
If your organization requires any of the above, the Enterprise Plan is the right fit.
Teams vs Pro Comparison
| Feature | Pro ($20/mo) | Teams ($45/mo) |
|---|---|---|
| Credits | 14,000 per month | 28,000 per month |
| Full model library | Yes | Yes |
| Smart Routing | Yes | Yes |
| Manual Pinning | Yes | Yes |
| Skills | Yes | Yes, team-shared |
| Projects | Yes | Yes, shared |
| Connectors | Yes | Yes |
| Collective Memory | No | Yes |
| Shared team workspace | No | Yes |
| Role-based access | No | Yes |
| Project sharing | No | Yes |
| Centralized billing | No | Yes |
| Usage management | No | Yes |
| Priority processing | Yes | Yes |
| Refund window | Yes | Contact support |
The jump from Pro to Teams is about collaboration. Pro is for an individual power user. Teams is for a group that needs shared context, shared skills, and centralized management.
Teams vs Enterprise Comparison
| Feature | Teams ($45/mo) | Enterprise (Custom) |
|---|---|---|
| Credits | 28,000 per month | Custom allocation |
| Collective Memory | Yes | Yes |
| Shared workspace | Yes | Yes |
| Role-based access | Yes | Yes |
| Projects | Yes | Yes |
| Skills | Yes | Yes |
| Models | Yes | Yes |
| Connectors | Yes | Yes, plus custom |
| Data residency | No | Yes |
| SSO/SAML | No | Yes |
| Audit logs | No | Yes |
| API access | No | Yes |
| Advanced governance | No | Yes |
| Dedicated support | No | Yes |
| White-label | No | Yes |
| Custom integrations | No | Yes |
The jump from Teams to Enterprise is about scale, compliance, and control. Teams gives you the full collaboration feature set. Enterprise adds the governance, security, and customization layers that large organizations require.
Who Should Choose Teams
The Teams Plan is built for:
Small teams of 3 to 10 people
who need shared context and collaboration
Growing organizations
that want knowledge to stay in the company, not in individual inboxes
Teams building shared skills
where one person's automation benefits everyone
Project-based teams
that need a shared workspace with collective memory
Organizations that need centralized billing
and usage visibility without enterprise compliance requirements
If your team is doing real work together and you are tired of context loss between tools, people, and sessions, Teams is the plan that fixes that.
Upgrade Signals
Consider moving to Enterprise when:
- You need data residency controls to meet jurisdictional or regulatory requirements.
- You require SSO/SAML for identity management across your organization.
- You need audit logs for compliance, security, or internal governance.
- Your credit usage exceeds 28,000 per month and you need custom credit allocation.
- You need API access to integrate Skynet into custom internal systems.
- You require custom integrations beyond the standard connector set.
- You need dedicated support with a direct relationship to the Skynet solutions team.
- You want white-label options for a branded deployment.
If any of these apply, contact sales to discuss an Enterprise plan tailored to your organization.
Refund and Billing Policy
Billing cycle
Monthly. Credits reset at the start of each billing cycle and do not roll over.
Centralized billing
One invoice for the entire team. Managed by a designated administrator.
Refund eligibility
The Pro Plan includes a refund within the eligible window after purchase. For Teams Plan refund terms, contact support through your workspace for specific eligibility details.
Plan changes
You can upgrade or downgrade your plan at any time. Changes take effect at the start of the next billing cycle.
For specific billing questions, contact support through your workspace.
Next Steps
Try Skynet. Start with a free account and explore the workspace. Upgrade to Teams when you are ready for shared context and collaboration.
Book a Demo. Schedule a walkthrough with our team to see how Collective Memory, Projects, and team-shared Skills work in practice.