Magazine
Akani, Launchpad, and NeuraLayer are now Architect
One composer for a picture, a clip, a page, a job, a gig, or a question. The old names stay on the API. The page you open is Architect.
Akani answered questions inside the product. Launchpad turned a conversation into a job or a gig. NeuraLayer built the picture, the clip, and the page. Those were three doors for one kind of work.
Open Architect: /architect
You land on a dark page. A greeting, two suggestions, and a composer. Plus and history sit at the top. The rest of the list is one click away.
Three names, one composer
Akani was the assistant: jobs, gigs, wallet questions, and the first draft of a listing. Launchpad was the create flow for that same listing, plus media when the brief needed a still or a page. NeuraLayer was the studio: image, video, HTML, and a website.
The split made you pick a product before you knew the result. “Make a mark, then a job for it” meant two tabs and two names.
Architect keeps the work and drops the choice. One thread holds the question, the file, and the draft you confirm. Existing nl_ keys and the launchpad path stay, so an agent that already calls them keeps calling them. The name on the page is Architect.
The empty start
A new chat is almost empty. The greeting uses your first name when the account has one. Two suggestions sit under it. The composer is centered on a wide screen and pinned to the bottom on a phone.
The two you see first follow what you have already made. A fresh account starts with Create an image and Write or edit. Plus starts another chat. The message icon opens the ones you already have.
Nothing on that screen is a free sample of the product. Sending a message spends credits. One credit is €0.01.
Architect
What should we make
plus · history · two suggestions
The rest of the list
The arrow beside the lower suggestion opens the rest. On a wide screen the list sits to the left of the composer and the greeting steps back. On a phone the list opens upward, over the bar, and the arrow points the same way.
The full set is the product:
- Create an image
- Write or edit
- Create a video
- Create an interface
- Create a job
- Create a gig
- Support
Tap one and that sentence is what you send. Architect asks for the missing detail, then does the work in the same thread.
arrow opens the rest of the list
A picture in the thread
Create an image asks for the subject and the style. You answer in the next line. The still shows up under the reply, in the chat, ready to keep or to attach to the next step.
Image models stay Nano Banana 2 and Gemini Pro Image, from 1K to 4K. The credit count is on the control before the run. The Build guide lists the resolutions.
still lands in the thread
Video, with the price first
Create a video asks for subject, style, and length. The price is on the screen before the clip starts. A short 720p clip and a long 4K clip are different bills, and both are visible first.
Video draws on purchased credits on the Free plan. On Pro and Business it draws on the included grant that arrives with the paid invoice. Bonus credits stay blocked for video on every plan.
The clip lands in the thread the same way a still does.
price first · bonus stays blocked
A page in the thread
Create an interface asks what the page should do, then shows a preview in the chat. A section, a landing page, or a small site stays in the conversation so you can change a line without leaving.
Auto sends that kind of work to the stronger text model. You can pin another model beside the composer when you want a lighter pass. The current lineup is in Claude 5.5 and Gemini 3.8 Flash.
Studio
preview stays in the thread
A job you can confirm
Create a job asks for the title, the budget, and what “done” means. The draft sits in the thread with those fields filled. You confirm it. Architect does the interview. You decide when it goes on the marketplace.
Escrow, delivery, and payout stay on the job after that. Architect writes the brief. The marketplace runs the money.
Job draft
you confirm · marketplace runs the money
A gig with three tiers
Create a gig asks what you deliver and how the three tiers should be priced. Basic, Standard, and Premium show up as one draft. You set the scope of each tier before it is public.
A gig is the packaged offer. A job is the open brief. The difference is the same as in Gigs vs jobs. Architect is where you write either one.
Auto, and what it costs
Auto is the default next to the composer. A short question stays on a light model. A page, a component, or a heavy prompt steps up. The control shows the credit range for that spread, from the light turn to the heavy one, before you send.
Every Architect message spends credits. There is no monthly pile of free messages on Free, Pro, or Business. Included credits on a paid plan arrive with the paid invoice. Bought credits stay until you spend them.
Support is the same composer when the question is the account: credits, a setting, a stuck step. It spends credits too.
every message spends credits