Your first edit
From “can we change this?”
to ready for review.
A visual and AI editor for your existing website. You shape the interface. Your developer connects the code and reviews the result.
Try your first edit- 01
Bring in the product you already have.
Create a team, then connect the repository that contains your website. GitHub users can choose repositories through the GitHub App. For GitLab or Bitbucket, your developer sets up the connection.
Not sure where your code lives? Choose Bring a dev. Create a setup link and share it with the person who manages the code. They connect the repository and configure its preview. You do not need their password or API token.
- 02
Start with one small, visible change.
Open the project and let its private preview build. Select a heading, button or other element, adjust the available visual controls, or describe what you want to change.
Try: “Change the homepage button text to Book a demo and give it more space above.” Check the result in the preview before making the next change. Use change history to inspect or undo confirmed edits.
- 03
Check it where your customers will see it.
Review the preview on phone and desktop. Look at text wrapping, button spacing and the path to the next action. Your workspace runs in the cloud; your phone does not have to build the application.
A preview can use test data or stubbed services. A successful visual preview does not prove that payments, authentication or other integrations work in production. Ask your developer to test the affected behavior.
- 04
Send a focused change for review.
Choose Send for review and explain what you changed and why. Revise prepares a pull request for GitHub or Bitbucket, or a merge request for GitLab, using the connected repository.
Your developer checks the actual code, tests it and decides whether to merge. Deployment follows your team’s usual process. Keeping each request small makes the review easier.
A good first project
A repository-backed website with a developer available to review changes. Start with copy, spacing, color or a small component update. Laravel and Angular repositories can be detected, along with other common stacks; custom setup may need developer input.
Read the setup and security detailsKnow what your trial covers
The trial has separate AI and workspace budgets. The workspace session includes build time and up to one hour of use. Save small changes and send them for review; temporary database data is not a permanent project backup.
See budgets and pricingBefore your first edit
A few things you might be wondering.
Do I need to know how to code?
No. Select an element and adjust it visually, or describe the change to AI. You do need access to an existing website repository. If someone else manages that, use Bring a dev to create a setup link for them.
Can I use my existing GitHub, GitLab or Bitbucket project?
Yes. Connect a GitHub App installation, or ask your developer to set up a GitLab or Bitbucket connection. Revise detects the stack and creates a separate preview. Custom services and private dependencies may need developer configuration.
Can I edit from my phone?
Yes. The workspace runs in the cloud, so you can preview and request changes from a phone or a computer. A larger screen is useful for detailed code review and layout work.
Will an edit change my live website?
Revise works in a separate preview. When you choose Send for review, it creates a pull or merge request. Your developer reviews and merges it through your usual workflow. Revise does not automatically publish the change.
Do I need an AI API key?
No. Eligible verified accounts receive a one-time trial AI budget to use Revise AI. Your team can also configure its own AI connection in Settings. Your own provider handles its charges and limits; it does not remove the workspace budget requirement.
What happens when my budget or preview session runs out?
New AI requests or workspace sessions pause when the required budget is unavailable. A workspace session covers up to one hour, including setup; temporary disks expire after 24 hours. Confirmed editor changes remain in history. Temporary database data and files created outside the editor are not retained. There are no automatic budget top-ups.