Roadmap

It was great to see the security enhancements for sites created with Stick light, but there is a huge gap in security. Sticklight accounts themselves do not have MFA. So, a Sticklight creator's account could easily be compromised and all sites, even if they each have very high security, are critically vulnerable to modification or deletion using Sticklight build tools.

Need more credits? With a saved payment method, you can continue working seamlessly even after your monthly limit is reached. Stay in control: Set a monthly spending cap to keep costs predictable. We’ll automatically pause extra usage once you hit your limit, so you only pay for what you use and never exceed your budget.

The concept: Buy digital products cheaply from wholesalers, put them on my own website, and resell them to my customers. Product categories. Licenses; Subscriptions; Software etc..

Problem Statement: Currently, the portal builder lacks visibility into active user sessions. When two developers (e.g., my co-worker and I) work on the same project simultaneously, we face a high risk of race conditions. Changes made by one user can be overwritten by the other upon saving, leading to lost work, configuration drift, and general frustration. Proposed Solution: We need a mechanism to manage concurrent editing. This could be approached in two ways, listed in order of preference: Option 1: Resource Locking (Session Blocker) Exclusive Edit Access: When a user opens a project or specific page, the system "locks" it for others. Presence Indicators: A visual badge showing "User X is currently editing this." Read-Only Mode: Other users can view the project but cannot save changes until the lock is released or a timeout occurs. Option 2: Real-Time Syncing (Collaboration Mode) Live Updates: Changes made by User A are reflected instantly on User B’s screen (similar to Google Docs or Figma). Granular Locking: Instead of locking the whole project, lock specific components or sections while they are being edited. User Stories: As a developer, I want to know if my teammate is already working on a specific page so I don't start making conflicting changes. As a project lead, I want the system to warn me if I’m about to overwrite someone else's more recent save. Success Criteria: Zero "Save Conflicts" reported during team builds. Visible UI indicators showing who is active in a project. A "Force Release" option for admins if a session lock gets stuck.

Let us edit a previous prompt/message and “rewind” from that point, without the whole chat / history feeling confusing. Key parts: Editing an earlier message creates a new branch/timeline from that stepKeep the original timeline intact (so nothing is “lost”)Show the timelines clearly (A/B, or simple number indicator under the message), with a one-click switch This is a super common workflow in AI builders that I like a lot.

Leverage a Multi-Streamable architecture to enable the simultaneous execution of multiple AI agents and UI updates within a single session, preventing execution bottlenecks. This allows for server-side persistence where complex tasks (like building multiple pages or running background scripts) continue independently of the user's browser state, ensuring a non-blocking, high-efficiency workflow

Connect your applications to n8n to enable powerful, low-code automation workflows and sync data with over 400 external services. This integration allows users to trigger complex background tasks, process data via AI agents, and bridge the gap between their Sticklight UI and enterprise software without writing custom backend logic

Implement clear, interactive UI buttons for actions requiring user consent (such as triggering Sticklight Cloud) to prevent users from waiting on a "hidden" chat request. This ensures the interface remains communicative and prevents project stalling by visually signaling when the system is awaiting a user’s "Go" or "Approve" signal.

Hi, I have a feature request regarding user management. I would like the ability to create and manage users inside Vibe Coding, including assigning roles and permissions. Ideally, there would also be an admin panel for user management where I can: Create and delete users Edit user information and access levels Assign roles and permissions Control what parts of the project each user can access View user activity and login history This would allow me to build applications with multi user access, team dashboards, client areas and more without needing to build the entire system from scratch. Is this something you plan to support in the near future? If possible, please consider adding this to the roadmap. Thank you.

the ability to clone platforms from base44/loveble/bolt into sticklight

Allow topping up an account with a bank of credits, as an addition to the monthly plan. This way a user could purchase as many credits as needed when more intensive work is required for a particular project.

Please add support for additional authentication providers beyond Google, including LinkedIn, Apple, and Facebook. This will reduce signup friction, improve conversion rates, and make the platform feel more natural for different audiences, especially professional users coming from LinkedIn and mobile users expecting Apple login support. Ideally, all providers should appear directly in the signup/login modal alongside Google with a unified onboarding flow.

Send an invoice to the user's email after a payment has been made.

It would be extremely useful if project management lived directly in the dashboard instead of inside individual projects. Things like: Creating and deleting projectsMaking folders and moving projects between themUnpublishing / publishing projects without opening themArchiving projects so they’re out of the way but not goneBasic bulk actions (select multiple → unpublish / delete / move) Once you have more than a handful of projects, the dashboard starts to feel like a flat list instead of a workspace. Folder support + lifecycle controls from the dashboard would make managing many experiments, clients, or iterations much faster and cleaner.

Implement a dedicated non-production environment (staging/sandbox) that allows users to test major updates, design changes, and feature integrations privately and thoroughly before deploying them live to the production website/app.

Implement full support for a Dark Mode theme across the entire Sticklight platform UI, including the dashboard, editor, and settings. Users can enable this feature in their preferences to reduce eye strain and match their operating system settings.

Integrate direct access to the Unsplash image library, allowing users to quickly search for, preview, and insert high-quality, royalty-free stock photography and visual assets into their Sticklight-generated application/website or presentations without needing to download and upload files manually.

I have an idea for how we can make using Sticklight even easier and more efficient for teams or friends. It would be fantastic if we could share a personal link or code that would allow, for example, a colleague, a team, or even a good friend to share the Sticklight page. This would allow us to test projects together, try out products, or evaluate features – without everyone needing a separate login. This kind of "shared testing" would not only facilitate collaboration but also encourage the exchange of experiences and feedback. I'm convinced that this feature would make working together with Sticklight even more attractive and practical – both for teams in their professional lives and for private users who enjoy discovering new things together.

Implement native integration that allows users to connect the Sticklight-generated front-end application to their existing Shopify store as a headless commerce solution. This feature enables the app to access and utilize Shopify's backend infrastructure for product data, inventory, checkout, and CMS, while providing a custom, high-performance front-end experience built by Sticklight.

Integrate an analytics dashboard directly into the Sticklight platform. This will provide users with essential, privacy-compliant, first-party data on their generated app/website's performance, including unique visitors, page views and top content without needing to install external tools like Google Analytics.

Integrate an automated audit tool that scans the generated app against major accessibility standards (e.g., WCAG 2.1/2.2). The tool will provide users with a report detailing issues related to color contrast, keyboard navigation, screen reader compatibility, and ARIA attributes, along with specific steps to ensure the site is usable by people with disabilities.

Integrate a built-in tool that performs an automated Search Engine Optimization (SEO) audit on the generated app. This feature will provide users with actionable feedback and scores on key on-page elements, including meta titles, descriptions, header structure (H1-H6), image alt tags, and overall content quality to maximize search visibility.

Implement a dedicated, intuitive visual editor (e.g., drag-and-drop or WYSIWYG) that allows users to manually adjust, refine, and customize the layout, styling, and content of the generated website/app without relying solely on the original prompt.

Enable users to import existing designs and layouts directly from Figma files to serve as a starting point or structure for their App

Implement support for Server-Side Rendering to improve initial page load times, enhance Search Engine Optimization (SEO) performance, and ensure that content is readily available to crawlers and users, particularly for dynamic content generated by the application.

Implement an integrated tool that analyzes and grades the generated app based on key performance metrics, such as Core Web Vitals (LCP, FID/INP, CLS) and general Page Speed. The feature will provide clear, actionable suggestions and optimizations (e.g., image compression, asset minification, and caching improvements) to ensure fast loading times and a smooth user experience.

Allow users to easily connect their generated Sticklight application/website to a Google Analytics property by simply inputting their Tracking ID (GA4 Measurement ID). This enables users to utilize industry-standard external tools for in-depth traffic analysis, user behavior tracking, and goal conversions.

Provide seamless, built-in support for Stripe, allowing users to quickly add secure payment processing, subscriptions, and checkout flows to their Sticklight application with minimal configuration, enabling immediate monetization.

It would be great to connect the Jira account and give access to Sticklight, so we can create visual dashboards, explore data, and present it using Sticklight.

This is a feature that will differentiate you from competitors and deliver clear added value. Credit management should be per project, not per account as it is today. Each project should be able to purchase and manage its own credits. For example: Project 1: I need 100 credits, so I’ll buy the $25 package for that project. Project 2: I need 200 credits, so I’ll buy the $50 package for that project. This would give users much better control and visibility. In addition, there should be an option to transfer credits from one project to another. Another topic - also a strong differentiator that would give your customers a major advantage: At the end of a project, when there is no longer a need for the minimum 100 credits package, there should be an option to purchase a package that includes: hosting, a custom domain, and removal of the Sticklight watermark. Today, the only way to get these benefits is through the 100 credit package, which means customers are paying for credits they no longer need.

Implement a dedicated, cloud-based Media Library where users can upload, manage, organize, and retrieve all visual and digital assets (images, videos, PDFs, custom fonts, etc.) used across their generated Sticklight applications and presentations. The library should include features like tagging, searching, and automatic optimization of assets for web delivery.

Implement a proactive scanning tool that automatically checks the generated application's code and dependencies for common security risks, vulnerabilities (like XSS or SQL injection potentials), and outdated libraries. The tool will provide detailed reports and prioritized recommendations for patching and improving the overall security posture of the deployed app.

Add option to add new users (like customers or colleagues) to join existing project so they can also edit the project.

Working on apps with friends/family/co-workers such that more than one person can edit the content

Implement deep, native integration to use WordPress as a Headless CMS by leveraging Rest API options. This allows users to manage content (posts, pages, products, etc.) through the familiar, powerful WordPress dashboard while leveraging Sticklight's output for a modern, high-performance, and secure front-end application.

Integrate a basic Speech-to-Text capability into the main prompt/chat box interface. This allows users to speak their request or description, and the system automatically transcribes the audio into text input. This improves accessibility and allows for faster articulation of long or complex prompts before generation.

Let us upload CSV files, which are useful for populating databases.

It would be extremely useful to add native support for uploading screenshots (PNG/JPG) and MP4 video files. This feature will allow users to: Upload and attach screenshots for clearer visual context. Upload short MP4 videos to demonstrate flows, bugs, UI behavior, or interactions. Improve communication and reduce back-and-forth explanations. Speed up feedback, debugging, and decision-making processes. Recommended details: Support MP4 video files with reasonable size limits. Inline preview for images and videos after upload. This enhancement would significantly improve usability, clarity, and overall user experience, especially for design, development, and QA workflows.

Implement an intelligent suggestion engine that offers relevant UI elements, animations, and functional enhancements based on the user's current project and prompts. By allowing users to select and apply multiple suggested improvements simultaneously, the platform eliminates the need for manual copy-pasting from external tools and streamlines the creative process.

It would be very useful to have a user-level preference .md file that applies across all projects. Right now, I often have to repeat the same instructions over and over again, such as coding preferences, design principles, project structure, naming conventions, accessibility requirements, and general workflow rules. A persistent preference file on user level would save time, reduce friction, and improve consistency across projects. This could include things like: • preferred coding style • preferred frameworks or implementation patterns • design and UX standards • do’s and don’ts • content and tone preferences • accessibility and SEO defaults It would make the system feel much more personalized and reduce the need to re-explain the same context in every new project.