Laxe | Know-how

We build web systems — and keep them online.

Laxe is a web development studio. We work on the core application, sign-in, registration, address processing, deposit and withdrawal flows, and the interface. We also offer website hosting, domain registration and related services.

Characters

Who covers each layer

Twelve figures. Each one carries a craft through to the end: access, records, money, the screen, and what stays online after launch.

Nara Voss The order of what you see, even when everything arrives at once.

16 years · order and reading

Arranges what a person meets first. Time, priority and a reading that does not repeat what was already shown. The whole set stays intact under load.

Kenji Arai The moment the screen and the server say the same thing.

14 years · realtime

Presence, state and ordered delivery. The connection drops and returns, and the place a person left is still there. Knows what stays on the device and what comes back from the server.

Lina Okada What comes in stays clear. What should not, stops.

18 years · judgment

Queue, priority and a record of the decision. Broad experience with volume, review, and removing what must go without erasing the rest of the work.

Mateo Cruz The right notice, at the right time, without excess.

15 years · notices

Who receives it, by which path, and when to stay quiet. Mass delivery, and a retry that does not repeat the same notice.

Sora Mendes Each person sees only what that account allows.

13 years · access

Sign-in, session and a trusted device. Each account has a clear slice. When the device leaves, the access leaves with it.

Hana Ito The next step is clear, without pushing what does not help.

17 years · next step

Interest, time and measured exploration. Separates what is only popular from what actually helps, and checks what the order changed.

Rafael Quintero Image and file arrive whole, in the right place.

12 years · files

Upload, conversion and delivery. A failure in one file does not take down the rest. The material stays available to the person who should receive it.

Yui Nakamura What gets written stays trustworthy.

19 years · trust

Limits, patterns and invites. Broad experience with misuse and with protecting what is published. The flow continues. The abuse does not.

Caio Brenner The history fits, and reading stays fast.

14 years · system memory

How a record is kept, split and read. Repairs what diverged without erasing what already happened.

Amira Sol A long list stays light in the hand.

11 years · screen

Lists, an early state and a later correction. The screen holds volume. Two people can write at the same time and not get lost.

Theo Lang Search finds, and respects what may be seen.

16 years · search

Index, suggestion and an almost-right name. The result fits what the account may open. An empty result still points to the next path.

Ren Kade The parts speak to each other. The system stays one.

15 years · the whole

The agreement between access, records, files and notices. Watches, forwards and cuts what does not fit. Command of the whole system, not of one screen.

Web development

Full-stack work on the system people actually use

We design and improve the core of the application: access, records, money movement and the screens around them.

Core application

The main web application: structure, screens and the flows that hold the product together.

Sign-in and registration

Account access and registration for new users, with a sign-in of their own.

What each person sees

Each account opens only the slice that belongs to it. The rest stays out of reach.

Records

Orders, accounts and movements stay stored in a way you can look up later.

Address processing

Capture, check and use addresses in checkout, delivery and account records.

Deposits and withdrawals

Clear money-in and money-out flows, from the order through to completion.

Progress

Each step shows a state: in the queue, in progress, ready, or when it could not be completed.

Interface improvements

Layout, language and interaction updates that make the same system easier to use.

Operations

Hosting, domains and related services

After the application is ready, it still needs a name on the internet, a server and mail that arrives.

How a project usually runs

Development, hosting and the domain stay in the same client area.

  1. 1

    Scope

    You tell us the application, the hosting and the domain you need.

  2. 2

    Build

    We work on the core system, access, addresses, money flows and the interface.

  3. 3

    Go live

    Hosting and the domain go online. You manage invoices and renewals in the client area.

  4. 4

    Support

    Tickets, knowledge base and the account stay in one place.

Agreement

The amount is the one agreed

For custom work, the accepted quote starts the job. The amount is that quote, the product price at order, or that period's invoice. A partial payment stays on the same invoice.

Terms of Service
Domains

Find a domain for the project

Search availability, then register or transfer. The name and the hosting stay in the same account.

Transfer Your Domain

Need the application, the hosting, or both?

Write to us about a development project, or open the catalog for hosting and domains.