Custom software development, built in your repo and your cloud

Custom software development means one team building every layer of a product and handing it over intact: the data layer, the backend, the frontend, and the deployment. Kaishift writes it inside your repository and runs it on your cloud accounts, with readable code, written documentation, and API keys that carry your name from the first commit. Your first working deliverable lands within weeks, and the first two weeks are refundable.

We build from Casablanca and deliver wherever the work is. This is Floor 2 of the tower.

Full-stack development, defined. One team owning every layer of a product: the database and its schema, the server-side logic and APIs, the interface people actually click, and the pipeline that puts it in production. No handoffs between three vendors, and no gap between them where the bug lives.

What do you actually get?

A platform, running, in your hands. Concretely:

• Backend. APIs, business logic, background jobs, and integrations with the systems you already pay for: CRM, billing, ERP, mail.
• Frontend. The dashboard, portal, or app your team and your customers use. Designed for the people using it rather than assembled from a template.
• Data. Schema, migrations, and access rules written down, so nobody has to guess what a column means a year from now.
• Deployment. Your cloud, your domain, your environment variables, with a build pipeline anyone on your side can run.
• Documentation. Written as we go, while the reasons behind a decision are still fresh.

Backend, frontend, and design ship as one product your team is using by month-end, readable line by line.

Who owns the code and the accounts?

You do, from day one. The repository is yours. The cloud account is yours. The keys are yours, and you can read them right now without asking us. We commit into your repo, deploy into your account, and document while we build, so the documentation is finished when the code is.

Anything we self-host for you is open source, so no licence line lands on your invoice. Pay-per-use services are billed to your own account, at cost, with no markup: model APIs, cloud, hosting. Own your stack: why your automation should run on accounts you control sets out the test we hold ourselves to, and the engagement itself runs on published terms with our own data handling in the privacy policy.

How does a build actually run?

Week one: access collected in one structured pass, scope written down, first commits landed. Within two weeks: something working in your hands. Within the first month: pre-production. After that, monthly cycles, and each cycle ends with something new deployed, documented, and running on your accounts.

You get a written record of what shipped, cycle by cycle. One senior engineer answers to you on the channel you already use, and directs the agent fleets that handle the repetitive part of the work. You can stop at any cycle and keep everything.

Why does building from Casablanca work for teams abroad?

Three practical reasons, and none of them is price.

We work your day, not your night. Casablanca sits at UTC+1, inside the working day of Europe, the Gulf, and the North American East Coast at once. A question asked in the morning gets answered the same morning, in the same working day.

We build in four languages properly. English, French, Arabic, and Spanish, including right-to-left layouts that hold their shape rather than mirrored CSS that breaks on the first long word. Our own site runs three of them. Most teams find out what retrofitting RTL costs only after launch.

Your data lives where your lawyers want it. Where the team sits and where the data sits are separate decisions. If the answer is Frankfurt or Paris, that is where we deploy. Morocco is the 55th state party to Council of Europe Convention 108, in force since 1 September 2019, which is the footing a European legal team usually checks first, though it is not an EU adequacy decision and we will not pretend otherwise. The EU AI Act reaches anything whose output is used in the EU, including systems built outside it, so we treat compliance as part of the build rather than a border to hide behind.

Who this is for, and who it is not

Good fit	Wrong fit
You have a product or an internal tool in your head and no engineering team to build it	You are shopping for the lowest hourly rate per body
You want the code, the repo, and the keys in your own name	You want a vendor to hold the system so you never have to think about it
You would rather see something running in two weeks than a full specification in six	You need a fixed price against a signed specification before a line is written
You expect to keep changing the thing after launch	The build is a one-off with nobody owning it afterwards
You are replacing spreadsheets, manual steps, or a tool that stopped fitting	You want a licence to a product that already exists

If the right-hand column describes you, say so on the call and we will tell you plainly. There are shops that do that work well. We are not one of them.

What do you build it with?

Whatever your team can maintain after we hand it over. In practice that means a current, boring stack: a typed backend, a modern frontend framework, Postgres for data, and self-hosted open source wherever it does the job. n8n for workflow orchestration, Supabase for data and auth, Coolify for self-hosting. When a build needs a model, it calls one through your key, billed to you at cost.

Where software is not the answer, we say so. Some problems are an automation or an agent, and we would rather ship the smaller thing that works. If your problem is closer to that, start with the AI agents floor or with workflow automation instead.

What happens after launch?

We stay. Monitoring on what we deployed, patches, and changes as the business moves. Most engagements run as monthly cycles for exactly this reason. Because everything runs on accounts you own, documented to match, you are accompanied rather than dependent. If you leave, nothing breaks and nothing is held hostage.

Talk to the person who scopes it

Thirty minutes with Sami Khalfi, who scopes every engagement himself. Amine Lamfichekh, our CTO, architects what gets built. You describe the workflow or the product, we map it, and the priced roadmap lands in writing within 48 hours. It is yours whether we work together or not.

Book a call with Kaishift, take the tower tour to see all five floors first, or read how we think about this work on the blog.

Common questions

What does full-stack development at Kaishift include?

One team builds every layer: database and schema, backend APIs and business logic, the frontend your users touch, and the deployment pipeline that puts it in production. Integrations with your CRM, billing, or mail systems are part of the build rather than a later phase. Documentation is written as we go, so your own engineers can take the project over.

Who owns the source code and the cloud accounts?

You do, from day one. We commit into your repository and deploy into your cloud account, using API keys registered in your name. Anything we self-host for you is open source, and pay-per-use services are billed to your account at cost. You can read the code and the keys at any time without asking us.

How quickly will we see working software?

Your first deliverable lands within two weeks: something running that your team can click through. Pre-production follows inside the first month. After that, engagements run in monthly cycles, each one ending with something new deployed and documented on your accounts. Those first two weeks are refundable if the first deliverable does not convince you.

Can you work inside our existing codebase or alongside our developers?

Yes. We commit into your repository, follow the conventions already there, and review with your team. Where you have in-house engineers, we work beside them rather than around them. A written record of what shipped is kept as we go, so nobody has to reconstruct the history from commit logs a year later.

Do you build interfaces in French, Arabic, and Spanish?

Yes. We ship English, French, Arabic, and Spanish, including right-to-left layouts built properly rather than mirrored at the last minute. Our own site runs three of them. For anyone selling in more than one language this is a requirement rather than a nice extra, so we plan it into the data model from the start.