Description
Summary AI AVATAR FACTORY – AUTONOMOUS 24/7 AI CONTENT PRODUCTION PLATFORM ABOUT NEVIE-GLOBAL NEVIE-GLOBAL is a French technology company developing an ecosystem around Artificial Intelligence, Enterprise Automation, SaaS, Blockchain, Robotics, IoT, Wearable Technology and Digital Education. We are building a next-generation Autonomous AI Avatar Factory capable of creating, managing, scheduling and publishing AI-generated content 24 hours a day, 7 days a week, with minimal human intervention. This is not a one-time assignment. We are looking for a reliable long-term technical partner capable of designing, developing, deploying, documenting and continuously improving the platform over an initial period of at least three months. Successful completion may lead to a long-term collaboration on multiple NEVIE-GLOBAL technology projects. PROJECT OBJECTIVE The objective is to build a scalable, modular, maintainable and production-oriented AI content platform able to automate the complete content production and publishing process. The platform must eventually manage: • Topic selection • Online research • AI script generation • Fact validation • Prompt management • Knowledge bases • AI agents • AI voice generation • AI avatar generation • Video rendering • Subtitle generation • Thumbnail generation • Title generation • Description generation • Hashtag generation • Multilingual content • Content scheduling • Automatic publishing • Multi-platform distribution • Performance monitoring • Analytics collection • Error management • Automatic retries • Email and Telegram notifications • Complete activity logging The technical architecture must support continuous autonomous operation and future growth without requiring a complete redesign. INITIAL COLLABORATION The initial collaboration will last at least three months. The project will be divided into clearly defined milestones. Each milestone must include: • Working source code • Deployment in the NEVIE-GLOBAL environment • Updated GitHub repository • Technical documentation • Installation instructions • Video demonstration • Testing evidence • Complete access and ownership transfer • Written validation before payment approval MONTH 3 MINIMUM TARGETS By the end of the initial three-month collaboration, the platform should support at least the following functions. AI AVATARS Minimum of 3 autonomous AI avatars. Each avatar must have: • Independent identity • Independent name and visual identity • Independent personality • Independent system prompts • Independent content strategy • Independent publishing schedule • Independent tone of voice • Independent audience positioning • Independent content history • Independent memory where technically appropriate • Independent analytics and performance tracking LANGUAGES Minimum languages: • English • French The architecture must allow additional languages to be added without major redevelopment. PUBLISHING PLATFORMS Primary publishing platform: • TikTok Minimum supported platforms by the end of the initial collaboration: • TikTok • YouTube • Facebook • Instagram • LinkedIn • X / Twitter The architecture must be modular and ready for future integration with: • Telegram • Discord • Threads • Pinterest • Reddit • Snapchat • Vimeo • Dailymotion • Other future platforms The long-term architecture should support more than 20 publishing platforms without major redesign. MINIMUM PUBLISHING CAPACITY Each avatar should be capable of automatically publishing at least: • 2 videos or posts per day on each supported platform With 3 avatars and 6 platforms, the minimum target is: • 6 TikTok publications per day • 6 YouTube publications per day • 6 Facebook publications per day • 6 Instagram publications per day • 6 LinkedIn publications per day • 6 X publications per day Minimum total target: • 36 fully automated publications every day The system must include safeguards against duplicate content, failed publications, incorrect scheduling and platform API limitations. COMPLETE AUTOMATION PIPELINE The complete workflow should automate the following process: Topic selection ↓ Research and information collection ↓ Source verification and fact validation ↓ AI script generation ↓ Editorial validation rules ↓ Voice generation ↓ Avatar generation ↓ Video rendering ↓ Subtitle generation ↓ Title generation ↓ Description generation ↓ Hashtag generation ↓ Thumbnail generation ↓ Quality-control checks ↓ Content scheduling ↓ Automatic publishing ↓ Publication verification ↓ Monitoring ↓ Logging ↓ Automatic retry of failed jobs ↓ Telegram and email notifications ↓ Analytics collection ↓ Performance analysis ↓ Continuous content strategy optimisation FIRST MILESTONE – TECHNICAL FOUNDATION The first milestone must establish the technical foundation of the platform. Expected deliverables: • Complete technical architecture proposal • Architecture diagram • Technology selection and justification • First operational end-to-end workflow • First autonomous content generation pipeline • First automatic publishing integration • GitHub repository created under NEVIE-GLOBAL ownership • Branching strategy • Development, staging and production environments • CI/CD pipeline • Docker environment • n8n workflows • API integrations • PostgreSQL database structure • Environment variable management • Secure credential management • Error handling • Basic logging system • Initial retry mechanism • Deployment documentation • Installation guide • Source code • Exported n8n workflow files • Database migration files • Video demonstration • Reproducible deployment The exact scope, acceptance criteria, deadline and payment for the first milestone will be agreed before development begins. TECHNICAL STACK The preferred technical stack includes: AUTOMATION • n8n • Webhooks • Scheduled workflows • Event-driven workflows • Queue management • Retry mechanisms LLM PROVIDERS Experience with several of the following is preferred: • OpenAI • Claude • Gemini • Grok • DeepSeek The architecture should avoid unnecessary dependency on a single provider. AI AVATAR PROVIDERS Experience with one or more platforms such as: • HeyGen • Synthesia • Tavus • D-ID • Creatify The system should use a provider-adapter architecture whenever possible so that providers can be changed or added later. VOICE PROVIDERS • ElevenLabs • OpenAI Text-to-Speech • Google Cloud Text-to-Speech • Azure Speech DEVELOPMENT • Python • Node.js • TypeScript • FastAPI • REST APIs • OAuth • Webhooks • JSON • Background workers • API rate-limit management INFRASTRUCTURE • PostgreSQL • Railway • Docker • GitHub • CI/CD • Secure environment variables • Backup systems • Monitoring tools DATABASE REQUIREMENTS PostgreSQL should manage information including: • Avatar profiles • Avatar prompts • Content strategies • Topics • Scripts • Sources • Generated assets • Videos • Audio files • Subtitles • Thumbnails • Publication schedules • Publication status • Platform accounts • Job history • Errors • Retry attempts • API usage • Token consumption • Costs • Analytics • Audit logs • User permissions The database must be structured, documented, secure and scalable. MONITORING AND LOGGING The platform must provide: • Complete job history • Workflow execution history • Success and failure status • Error details • Retry counter • Publishing logs • Publication identifiers • API response logs • API usage monitoring • LLM token consumption monitoring • Avatar generation cost monitoring • Voice generation cost monitoring • Platform publishing status • Telegram alerts • Email alerts • Health monitoring dashboard • Daily operational summary • Failed-job reporting • Manual reprocessing option • Audit trail SECURITY REQUIREMENTS The selected partner must apply professional security practices. Required principles: • No credentials stored directly in source code • No API keys committed to GitHub • Secure environment variable management • Restricted access permissions • Role-based access where appropriate • Secure OAuth implementation • Secure webhook validation • Protection against unauthorised workflow execution • Regular backups • Recovery procedures • Documentation of all administrator accounts • Removal of developer access at the end of the collaboration if requested DOCUMENTATION Complete documentation must include: • Installation guide • Deployment guide • Configuration guide • User manual • Administrator manual • Developer manual • API documentation • Database documentation • Workflow documentation • n8n workflow inventory • Environment variable documentation • CI/CD documentation • GitHub repository structure • Backup procedures • Disaster recovery guide • Monitoring guide • Troubleshooting guide • Provider integration guide • Platform publishing guide • Maintenance procedures • Upgrade procedures SUCCESS CRITERIA By the end of the initial collaboration, the platform should demonstrate: • Stable autonomous execution • Reliable automatic content generation • Reliable automatic publishing • Minimum 3 operational AI avatars • French and English support • Minimum 6 publishing platforms • Minimum target of 36 publications per day • Modular architecture • Clean and maintainable source code • Complete logging • Automatic retry system • Monitoring and alerts • Reproducible deployment • Complete documentation • Easy maintenance • Production-ready technical foundation • Complete ownership by NEVIE-GLOBAL OWNERSHIP AND TRANSPARENCY All repositories, cloud resources, databases, workflows, deployment environments and project assets must be created under NEVIE-GLOBAL ownership whenever technically possible. This includes: • GitHub repositories • Railway projects • PostgreSQL databases • n8n environments • Domain configurations • Cloud services • OAuth applications • API accounts • Monitoring tools • Documentation • Source code • Workflow exports • Infrastructure configuration The following are strictly prohibited: • Hidden administrator accounts • Hidden API keys • Hidden repositories • Hidden credentials • Undeclared external services • Obfuscated code • Undocumented dependencies • Personal developer accounts controlling production resources • Vendor lock-in created without written approval After payment for each milestone, all delivered source code, documentation, configurations and intellectual property related to that milestone must become the exclusive property of NEVIE-GLOBAL. WORKING METHOD The collaboration will follow these principles: • Milestone-based development • Written communication • Regular progress reports • Clear deadlines • Clear acceptance criteria • GitHub commits throughout development • Code review • Technical demonstrations • Video demonstration before milestone acceptance • Testing before validation • Complete documentation • Transparent technical decisions • Reproducible deployment • Complete source code transfer • Complete intellectual property transfer A milestone will not be considered complete based only on screenshots, mock-ups or verbal explanations. The delivered system must be operational, testable and reproducible. REQUIRED EXPERIENCE Strong practical experience with most of the following is expected: • AI automation systems • n8n production workflows • OpenAI, Claude or Gemini APIs • AI avatar platforms • Automated video generation • Automated social-media publishing • PostgreSQL • Railway • Docker • GitHub • CI/CD • REST APIs • OAuth • Webhooks • Python • Node.js • TypeScript • FastAPI • Monitoring • Logging • Retry systems • Production deployment • Technical documentation Experience building real production AI automation systems is strongly preferred. APPLICATION REQUIREMENTS Please provide all of the following information: 1. Short professional introduction 2. Number of years of experience 3. Country and time zone 4. Solo developer or team 5. Weekly availability 6. Proposed start date 7. GitHub profile 8. LinkedIn profile 9. Portfolio 10. Relevant AI avatar projects 11. Relevant AI automation project