# elizaOS Discord - 2026-05-06

## Summary

### Payment Infrastructure Integration

odilitime announced that elizaOS and DegenAI were added as default payment methods in elizaOS for x402 routes, marking a significant milestone in payment system integration for the platform.

### Project Consolidation and Infrastructure

Shaw reported that ElizaCloud has been consolidated into the main eliza repository at github.com/elizaOS/eliza. The team migrated away from Vercel hosting to support cheaper container solutions, implementing cost optimization measures for operational efficiency.

### Project Structure and Governance

Shaw clarified that elizaOS operates as a fair launch project without VC backing or traditional team structure. The project consists of builders who use and develop the technology, with the platform enabling developers to build and monetize their own applications on top of the infrastructure. Shaw emphasized that the founder's role focuses on product development rather than token price management.

### Unanswered Technical Inquiries

Several technical questions were posted without resolution, including guru0's inquiry about cloud hosting costs for running Eliza as a Twitter bot and Mac mini hardware feasibility, and binarycookies' question about Hyperfy connectivity status for elizaos.

## FAQ

**Q: Where is ElizaCloud now located?**
A: ElizaCloud has been consolidated into the main eliza repository at github.com/elizaOS/eliza.

**Q: What hosting changes were made to ElizaCloud?**
A: The team migrated away from Vercel hosting and implemented support for cheaper container solutions to reduce operational costs.

**Q: What is the organizational structure of elizaOS?**
A: elizaOS operates as a fair launch without VC backing or traditional team structure, consisting of builders who use and develop the technology.

**Q: What payment methods were added to elizaOS?**
A: elizaOS and DegenAI were added as default payment methods for x402 routes.

**Q: What is the founder's primary focus?**
A: The founder focuses on product development rather than token price management.

## Help Interactions

No resolved help interactions were documented in the provided channel summaries. Multiple questions were asked but remained unanswered, including guru0's questions about hosting costs and hardware requirements, and binarycookies' inquiry about Hyperfy connectivity.

## Action Items

### Technical

- Maintain consolidated repository structure at github.com/elizaOS/eliza following ElizaCloud migration (mentioned by Shaw)
- Continue supporting cheaper container solutions for cost optimization (mentioned by Shaw)

### Documentation

- Direct users to consolidated GitHub repository for ElizaCloud-related inquiries (mentioned by Shaw)