> This page is for The Console. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://infonite.dev/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://infonite.dev/_mcp/server. # Your first application An application is the unit of everything technical on INFONITE — its own keys, its own webhooks, its own customers, sealed from every other application on the platform ([why that matters](/console/organizations-and-applications#the-applications)). You create it yourself, and you can create as many as you need. > **Note** > > **Creating one costs nothing and commits you to nothing.** A new application runs in the sandbox against rehearsal data, so the whole integration can be written and tested before anybody at INFONITE is involved. --- ## Creating it From the **application selector** at the top of the Console, **Create new app** at the foot of the list — and if your organization has none yet, the Console offers it on the screen that says so. It opens over whatever you were looking at; closing it puts you back there. ![The Create New App sheet in the Console: the logo placeholder, the note that every application is born in the sandbox, the public display name with a live preview of the consent screen on a phone, and the fields for the internal name, website and contact email](/_fern-files/_img/d4fe3c73a267e20ebd453faa99bcc88e13e80d4f05e47971713769f2be245727.webp)![The Create New App sheet in the Console: the logo placeholder, the note that every application is born in the sandbox, the public display name with a live preview of the consent screen on a phone, and the fields for the internal name, website and contact email](/_fern-files/_img/3945e424ca69ca7e0ddd5496a3d81ef49c1513645f566c53c5a5e4e9a1924182.webp) #### The public name — choose it carefully It is what your end users read on the consent screen, and the phone beside the field shows them reading it as you type. **It is frozen once the application exists**: people recognise your service by that exact name, so it is not ours to let you change quietly. Everything else on the screen can be edited whenever you like. #### The internal name A private label, only your Console ever shows it. It starts as a copy of the public name and you can take it anywhere — *Loans — staging*, *Verification v2*. Rename it as often as you want. #### Website and contact email Optional, and both are for us: where your service lives, and the mailbox we write to about this application. Neither reaches your end users. --- ## What it can do straight away **Everything — in the sandbox.** Every capability is available from the first minute, against rehearsal data that never touches a real institution or a real person. That is the whole point of the environment: you build and test the integration end to end, and the only thing left afterwards is the decision to go live. #### [Get the secret](/console/security-and-keys) Your backend needs an application secret to call us at all. Mint it on **Security & Keys**. #### [See what it may do](/console/capabilities) The **Capabilities** screen lists every capability and how far each one reaches today. --- ## Asking for production Production is **a request, not a switch** — and it is a conversation, because in production your application reaches real people and their real data. You raise it from the application itself: *App Settings → General*, on the card that carries the public name. ![The Ready to go live invitation on the General settings of an application in the Console, with the Promote button](/_fern-files/_img/0e7a15047a6364d1f4a87705806698664bc635332f84d0b84be5116b3fcfde24.webp)![The Ready to go live invitation on the General settings of an application in the Console, with the Promote button](/_fern-files/_img/c8e18fe27941149cae7c99911644c85585bd58fbc0ae84396b1206a439df935c.webp) **Promote** opens two steps. ### Step 1 — What gets protected ![Step one of the promotion request: what we protect from here on — the visual structure, the system colours and the logos, and the flows' texts and documents](/_fern-files/_img/7928c4b219b03589c56ac3be2f7c3a9246d20c13d9c3cb5a2fd8472e6a5666d7.webp)![Step one of the promotion request: what we protect from here on — the visual structure, the system colours and the logos, and the flows' texts and documents](/_fern-files/_img/2562eea12ce9070eae1dce8081f40a3ffab6d11317d0d49db0ce8a54b74b16dc.webp) From the moment you ask, the application's **face** stops being yours to change on your own: the visual structure and the system colours, the logos, and the texts and documents the widget shows. Your users recognise your service by those, and a live brand that can change without anyone reviewing it is a brand nobody can vouch for. You keep seeing it and keep trying out how it would look. What changes is that publishing goes through a request we review with you — a record on every change to your brand, rather than a door that closes. > **Warning** > > **The freeze starts with the request, not with the approval.** While an ask is open the aesthetics are already read-only. If that turns out to be too early for you, the request can be withdrawn from the same card — the corner **×** — and the application goes back to being fully yours. ### Step 2 — What it will be able to do ![Step two of the promotion request: the list of products with checkboxes, those already live or already asked for marked as such, and an optional message field](/_fern-files/_img/e921b5f2db111e071d3d93432db97b0779c20bac3a9319ab960d5d434293c789.webp)![Step two of the promotion request: the list of products with checkboxes, those already live or already asked for marked as such, and an optional message field](/_fern-files/_img/360152af961d8b1f1246e81825b952d00a7ddf17b5e3426ffc4a1bde96cf25f0.webp) A live application that can do nothing is not much use, so the same form asks for **at least one product**. Anything already granted or already waiting on us counts — nobody is asked twice for something that is already in our queue — and the rest of the [catalogue](/console/capabilities) can be requested any day from its own screen. The message under it is optional and it is the part a person reads before deciding. What you need it for, when you go live, what you have already tested: any of it shortens the conversation. ### While it is with us ![The same card once the request is open: Your request is with us, the date it was asked, and a discreet close button to withdraw it](/_fern-files/_img/f3e2216526726323817bdaca4696d86ff31af30cbe812471379a669e18332564.webp)![The same card once the request is open: Your request is with us, the date it was asked, and a discreet close button to withdraw it](/_fern-files/_img/5babb50d8145044faff6f66858a0da550f532ec47162104631994709186c8716.webp) The card says so, with the date. One submit raises **several** asks — the move to production, plus one per product you ticked — because they are separate decisions: we may grant a product and hold the promotion, or the reverse. Each is answered on its own, and the products are tracked on the [Capabilities](/console/capabilities) screen. Withdrawing the promotion from the **×** withdraws *only* the promotion; the product requests stay where they are, and you take those back one at a time from their own screen. --- ## Next #### [App settings](/console/app-settings) The names, the redirect URLs, and the danger zone — everything on the General section. #### [Security & keys](/console/security-and-keys) The secret your backend signs in with, and the optional encryption pair.