Skip to content
kalevala.dev
  • Pricing
Contact sales

Serious software for companies that need it to work the first time. Enterprise AI integrations, high-security code, and projects that start within 24 hours.

toimeksianto@kalevala.dev

Site

  • Solutions
  • Products
  • Work
  • Hustles
  • Docs
  • Trust
  • Pricing
  • Contact

Read first

  • How we work
  • The 24-hour kickoff
  • Security practices
  • You own everything
  • How pricing works
<kalevala.dev>
© 2026 Kalevala.dev · Privacy · Image credits ·

Trust you can check.

Trust is not a claim on a website. It is a charter you sign, a status note every Friday, invoices that match what was agreed, and documentation you keep. Here is exactly how we work with you.

How we build trust

Four promises we keep on every project, whatever its size.

Everything in writing
Scope, changes, dates, prices and the access you give us. Nobody has to remember what was said on a call.
You own it from day one
Code, accounts, domains and data are created in your name. We are invited, and can be removed in one click.
You see the work as it happens
A test address from the first week, a weekly status note, and the repository open to you the whole time.
No surprises on the invoice
A fixed price per deliverable, invoiced at agreed points. A change in scope is priced before it is built.

Kickoff within 24 hours

Once the charter is signed and the deposit is in, work starts the same or the next working day. By the end of that first day the repository, the hosting and a test address exist on your own accounts, and you have the first status note.

The kickoff, hour by hour
  • Repository created in your organisation, you invited as owner
  • Hosting and domains set up in your company's name
  • A test address live, even if it only says hello
  • The charter's done checklist turned into tracked tasks
  • First written status sent before the day ends

The charter

Every project starts with a one-page charter. It names the deliverable, says what done means in checks anyone can verify, and fixes the price, the date and who does what. It is the document both sides point to if a question ever comes up.

How we scope
charter.txt
PROJECT CHARTER

Client         Your company Oy
Deliverable    Customer portal: login, orders, invoices, PDF export
Done means     12 checks, listed and signed (see appendix)
Price          Fixed, 40% deposit, 60% on acceptance
Kickoff        Within 24 hours of the deposit
Delivery       A fixed date, agreed in writing
Test address   test.yourcompany.fi, from week one
Status         Written note every Friday
Your contact   One named person, replies within 1 working day
Accounts       Created in your company's name
Changes        Priced and signed before they are built

The path

The same seven stages for every project. You always know which one you are in and what comes next.

  1. Day 0

    Brief

    You tell us what you need, in your own words. We reply the same day with questions, a first shape and a price range.

  2. Days 1–3

    Scope and charter

    One deliverable, written down: what done means, the date, the price and who does what. You sign the charter and pay the deposit.

  3. Within 24 h

    Kickoff

    The repository, hosting and a test address exist on your accounts by the end of the first day. You get the first status note.

  4. Weekly

    Build

    Changes land on the test address first. Every Friday a short written status: done, next, blocked, and anything we need from you.

  5. Agreed date

    Acceptance

    You click through the test address against the done checklist in the charter. We fix what is off, then it goes live.

  6. Delivery

    Handover

    Documentation, a recorded walkthrough, every account and key confirmed in your name, and the final invoice.

  7. 30 days +

    Support

    Thirty days of fixes are included. After that, a small monthly plan, or nothing at all: the system runs without us.

Documentation you keep

Written as we build, not at the end, and handed over with the system. If we disappeared tomorrow, your next developer could carry on.

Project charter
The one-page agreement behind every project. Signed before work starts.
README
How to run, test and deploy the system. A new developer can start from it in an afternoon.
Architecture notes
What the parts are, how they talk to each other, and why it was built this way.
Decision log
Every significant choice, when it was made, the options and the reason.
Runbook
What to do when something breaks, written for the person on call, not for us.
Handover pack
Accounts, keys, contracts with third parties and the recorded walkthrough, in one place.

Invoices and routine status

A short written status every Friday, in plain words: what was done, what is next, what is blocked and whether the date and budget still hold. Invoices arrive at the points the charter names, and never for anything you did not agree to first.

Deposit
When the charter is signed. Work starts within 24 hours of it.
On acceptance
The rest, once you have accepted the deliverable against its checklist.
Monthly work
One invoice a month with the hours or the plan, itemised.
Format
A PDF invoice in euros, with your reference or purchase order number on it.
status-week-3.txt
STATUS · week 3 · Friday

Done      Login with email links; orders list with filters
Next      Invoice PDFs; Finnish translations
Blocked   Need the logo in SVG from you
Budget    On plan (deliverable 1 of 2)
Date      On track for 14 November
Test      test.yourcompany.fi (updated today)

Ask us anything before you decide.

A question costs nothing. Ask for a sample charter, a reference, or how we would approach your project, and a person replies within 24 hours.

Contact ustoimeksianto@kalevala.dev