# Mixpost Lite: a self hosted social media scheduler with a Lite and Pro split > A Laravel and Vue application for scheduling posts across social networks, distributed under MIT as the Lite edition of a commercial product with clear rules about what stays separate. **inovector/mixpost** — 📅 Schedule, 📢 publish, and ⚡ manage your social media content on your server. No subscriptions, no limits. (Buffer alternative) - Repository: https://github.com/inovector/mixpost - Website: https://mixpost.app - Stars: 3,854 · Forks: 582 - Language: Vue - License: MIT - Published: 2026-10-06 · Updated: 2026-10-06 · Language: en - Canonical page: https://hysenlabs.com/projects/inovector-mixpost ## The README sells features, the contributing guide sets the boundary Read this project the other way round from most and the substance appears early. The README is a product page: it calls Mixpost a social media management platform, describes scheduling content for when an audience is engaged, and lists features such as a media library, post templates, dynamic variables, hashtag groups, team workspaces and calendar and queue management. It positions itself as a Buffer alternative with no subscription and no limits, aimed at enterprises, small and medium businesses, agencies, solopreneurs and e-commerce stores. The paragraph with actual engineering weight comes under contributing, and it says something a buyer should know before deploying: this repository contains the Lite version of Mixpost Pro, which is a commercial product. Contributors are asked to open an issue before writing a feature, with the reason given plainly, that Lite features must remain distinct from those in Mixpost Pro. Optimisation and bug fix pull requests are welcomed without that ceremony. That is a healthy norm for an open core project and an unusual thing to see stated this clearly. It also tells you that feature parity with the paid edition is not the goal, so an evaluation should not assume the free version is the product with a price tag removed. ## A Laravel backend with a Vue 3 frontend and Inertia The topic list names Laravel and PHP, and the repository tree confirms a conventional Laravel application layout with `app/` style structure split into `src/`, `config/`, `routes/`, `resources/` and `database/`, alongside `composer.json`, `phpunit.xml.dist` and `vite.config.js`. The frontend dependency list is more informative than the README. Vue is at 3.5, and the key integration choice is `@inertiajs/vue3`, which is how the Laravel backend serves rendered pages to a Vue application without either a separate SPA deployment or traditional server rendered templates. That single choice explains a lot about the structure: you get one application process, one build step and no second service to host. The rest of the frontend stack is worth scanning for the project's centre of gravity. TipTap provides the rich text editor with its document, history, link, placeholder, text and typography extensions. `chart.js` with a zoom plugin handles the analytics views, `date-fns` and `date-fns-tz` handle scheduling across time zones, `vuedraggable` handles reordering, `vue-flatpickr-component` the date picker, `floating-vue` tooltips and `emoji-mart-vue-fast` with `twemoji-parser` the emoji handling. `ziggy-js` generates route helpers, and `twitter-text` is present for tweet text validation. A detail that shows real production attention: release 2.4.0 migrated fonts from TTF to WOFF2 for better performance, alongside adding Facebook Graph API v24.0 support. Performance work that nobody asks for in an issue tracker usually means someone was actually loading the thing. ## Follow the release notes to see what actually changes The tagged releases are a good indicator of where the effort goes, and for a social media scheduler the answer is upstream API compatibility rather than new UI. Version 2.6.0, published 2026-03-16, added support for the X pay-as-you-go tier. Version 2.5.0, published 2026-02-24, added Facebook API v25.0 support. Version 2.4.0 from November 2025 added Facebook Graph API v24.0 and the font change. Two of the three most recent releases are Facebook Graph API version bumps. That pattern is the honest cost model of this category of software. Your scheduler is only as good as the newest API tier each platform offers, and platforms version their APIs on their own schedule. A project that keeps up is doing real work even when its changelog looks like a list of version numbers, and a project that stops will start failing quietly in production as old API versions are retired. The last push on the default branch was 2026-03-16, the same day as the 2.6.0 tag, so nothing has landed since. That is recent enough that the API story is not yet a concern, but it is a gap to keep an eye on if you are choosing a platform for the next few years. ## Installation lives in the docs, not the README The installation section of the README is two lines long, and the first of them points you at the documentation: read the Lite documentation on how to get started. That is a deliberate choice for a product with a paid tier, since getting a Docker or Composer deployment right for an arbitrary environment is exactly the kind of content that goes stale. What the repository does tell you is the shape of the configuration. There is a `.env.example` at the root, and in the Lite version it is a single line: ``` APP_URL=http://localhost ``` That is a real signal about the deployment model. The Lite edition expects to be installed as a package into a Laravel application you control, with the application key, database credentials and platform API credentials added as the docs instruct, rather than run as a single opaque container. There is no `docker-compose.yml` in the tree, which supports that reading. The consequence for you is that you are running a Laravel application, not a finished product. You will be responsible for the PHP version, the queue worker that actually fires scheduled posts, the cron entry that runs the scheduler, and the storage that holds uploaded media. That is more responsibility than a hosted service asks for and considerably less than building this yourself. ## What the repository does not tell you Several practical questions cannot be answered from the repository. Which social platforms the Lite edition connects to is not enumerated anywhere in the README, and since the recent changelog is all Facebook and X, the platform list is something you have to confirm in the docs or the demo before committing. Whether there is a limit on connected accounts or scheduled posts in Lite is likewise unstated, which matters given the no limits claim in the description. The changelog is also referred rather than included. The README links to the releases page instead of carrying a changelog file, even though `CHANGELOG.md` is present in the tree, so the detailed history of features between minor versions is not visible from the README. Two smaller things worth knowing. The project credits Dima Botezatu, and it is sponsored and supported by Inovector, which is the commercial operation behind the Pro edition. Security issues go through a security policy rather than public issues. And the repository carries 3,734 stars with 567 forks and 35 open issues, so there is real usage and an active issue queue, even though the public discussion volume is modest. ## Conclusion Mixpost is a credible choice when you want to own the scheduling layer and run it on your own infrastructure, and the repository makes the important boundaries explicit rather than hiding them. The Lite edition is MIT licensed and genuinely self contained, with a Laravel backend, a Vue 3 frontend and a documented installation path. The real decision is whether you need the Pro features, and the contributing guide is unusually clear that Lite and Pro feature sets must not bleed into each other. Start with the Lite documentation, install it, and check the platform list before planning a migration, since this project updates its API integrations as those platforms change. ## FAQ ### What is the difference between Mixpost Lite and Mixpost Pro? The README says this repository holds the Lite version of Mixpost Pro, which is a commercial product. Lite is released under the MIT license and contributors are asked to keep Lite features distinct from those in Pro, so the free edition is not the paid product with features removed. The documentation on the project site covers the difference in practice. ### Is Mixpost a free alternative to Buffer? That is how the project positions itself, as a Buffer alternative with no subscriptions and no limits. Since you host it yourself, the tradeoff is operational rather than financial: you run the Laravel application, the queue worker and the scheduler yourself. The README also notes the free Lite edition is intended to stay distinct from the paid Pro tier. ### What tech stack is Mixpost built on? A Laravel PHP backend with a Vue 3 frontend wired together through Inertia, so there is no separate SPA to deploy. The frontend manifest shows TipTap for rich text, Chart.js for analytics, date-fns for scheduling, and libraries for emoji handling, drag reordering and flatpickr date picking. Vite handles the asset build. ### How do I install Mixpost Lite? The README points to the Lite documentation for setup rather than including instructions. The repository shape suggests a Composer package installed into a Laravel application you control: the root `.env.example` contains only an `APP_URL` line, and there is no compose file in the tree. Platform API credentials and application configuration are added per the documentation. ### Which social platforms does Mixpost support? The repository does not enumerate the supported platforms, so this needs checking in the documentation or the demo. Recent releases give a hint about direction: version 2.5.0 added Facebook API v25.0 support and 2.6.0 added the X pay-as-you-go tier, so Facebook and X integration work is where recent effort has gone. ## Sources - [inovector/mixpost on GitHub](https://github.com/inovector/mixpost) - [License: MIT](https://github.com/inovector/mixpost/blob/main/LICENSE) - [Project website](https://mixpost.app) - [README](https://github.com/inovector/mixpost/blob/main/README.md) - [Releases](https://github.com/inovector/mixpost/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/inovector-mixpost