Shared responsibility¶
Buying Vellocity through AWS Marketplace crosses two clean boundaries. This page shows where responsibility hands off between AWS, Vellocity, and you — the integrator — so you never have to think twice about which side of the line something lives on.
1YouSubscribe
→
2AWSEntitle
→
3VellocityProvision key
→
4YouIntegrate
→
5VellocityMeter
→
6AWSBill & settle
The rail
AWS
Procurement & billing
- Hosts the Marketplace listing
- Runs subscription, invoicing & payment
- Draws down your EDP commitment
- Emits entitlement events on subscribe / cancel
- Settles funds to the seller in USD
↔entitlement token · SNS
The platform
Vellocity
The engine you resell
- Provisions your
vp3_key ● auto - Runs the capabilities on Amazon Bedrock
- Serves & maintains the MCP endpoint
- Meters every call & bills through AWS
- Revokes on unsubscribe ● auto
- Uptime, security & tenant isolation
↔vp3_ key · MCP endpoint
Your side
You
The integrator (3PI)
- Subscribe on AWS Marketplace
- Store the
vp3_key securely - Integrate the MCP endpoint into your product
- Serve & support your customers
- Set your markup / rev-share
- Stay within acceptable-use terms
Rule of thumb: you own the key and the customer relationship; Vellocity owns the platform and the metering; AWS owns the money movement. Anything marked ● auto happens on subscribe or cancel — no manual handoff.
In plain terms¶
If the diagram doesn't render, this is the same split:
| Responsibility | Owner |
|---|---|
| Marketplace listing, subscription, invoicing & payment | AWS |
| Drawing spend down against your EDP commitment | AWS |
| Entitlement events (subscribe / cancel notifications) | AWS |
| Settling funds to the seller of record (USD) | AWS |
Provisioning your partner account + vp3_ key (automatic) |
Vellocity |
| Running the capabilities on Amazon Bedrock | Vellocity |
| Serving and maintaining the MCP endpoint | Vellocity |
| Metering every call and billing it through AWS | Vellocity |
| Revoking access when you unsubscribe (automatic) | Vellocity |
| Platform uptime, security, and tenant isolation | Vellocity |
| Subscribing on AWS Marketplace | You |
Storing the vp3_ key securely and rotating it |
You |
| Integrating the MCP endpoint into your product | You |
| Serving and supporting your own customers | You |
| Setting your markup / rev-share | You |
| Staying within usage & acceptable-use terms | You |
The two boundaries¶
- AWS ↔ Vellocity — what crosses is the entitlement: an AWS token plus SNS lifecycle events. Vellocity acts on them (provision on subscribe, revoke on cancel). You never touch this handoff.
- Vellocity ↔ You — what crosses is your access: the
vp3_key and the MCP endpoint. From there, how you build on it and who you serve is yours.
See also: Getting Started · Authentication & API Keys · Usage & Billing.