We launched an API & MCP-first image engine. What should we build next?
Hey Product Hunt! 👋
Now that the core engine for PixelDrive is live and the API is humming along nicely, I'm looking closely at our immediate product roadmap. Instead of guessing, I want to build exactly what you need to scale your visual automation workflows.
To give you a quick recap of what's under the hood right now:
19ms Global Edge Caching: Identical requests completely bypass compute, serving images instantly at exactly 0 credit cost.
Hosted MCP Server (26 Tools): Built natively so AI agents (like Claude or Cursor) can programmatically spin up templates, read layers, and autonomously nudge layout coordinates to fix text wrapping.
Vector Layout Engine: No heavy, slow headless browsers (Puppeteer/Playwright).
Which of these features or integrations would make PixelDrive a permanent part of your tech stack?
🔌 Official Figma Plugin: Design visually in Figma and instantly export to a programmable PixelDrive template with your text/image variables fully intact.
📦 First-Party SDKs: Dedicated Node.js and Python wrappers to make backend integration even faster.
🗄️ Native Database Sync: Automatically generate graphics whenever a new row or product is added to Supabase, Airtable, or PostgreSQL.
Reply with 1, 2, or 3 (or drop a custom feature request)! I'm reading and replying to every single comment today. Let's build the future of programmatic design together! 🛠️
Replies