Blog
Most software companies publish what they decided. These are the reasons, including the decisions that cost us something, and the ones we would rather you heard from us.
Every office suite you can name is free, subsidised, or the doorway to something else. So we did not try to sell ours. We sell the engine underneath it, and the speed to close a gap you still have.
· 6 min read
If you have paid for time you are not using, there is a button that gives it back. No window, no reason, no email to support. Here is exactly how the number is worked out, and where we round.
· 4 min read
More
Ten short films now show the Rutba Suite doing a day’s work: a corner shop, a wholesaler, a takeaway, a garden centre, a furniture workshop and a building firm, all invented, each using the apps for what that business actually needs.
A three and a half minute film follows Larkspur Corner Store, an invented shop, from its website through the CMS behind it to a cash sale at the till and the day’s takings. Every price and stock figure on the way comes from one catalogue.
A three minute film follows Northbank Trading, an invented wholesaler, through its stock, a warehouse laid out to the bin, a delivery received against its order, a draft purchase for what has run out, and the stock valued at cost.
A three minute film follows one order at Saffron Lane, an invented takeaway that delivers its own food: across the order board, packed in Dispatch, onto a rider’s run, signed for at the door, and followed by the customer on a tracking page with no account.
A three minute film follows the sales team of Northbank Trading, an invented wholesaler, from a board of leads to a logged call, then a customer’s question about a late order answered in Helpdesk, with every step landing on the same contact page.
A four minute film follows Wrenmoor Garden Centre, an invented business with a nursery and a cafe, through a leave approval, a tablet paired as the staff clock, a clock-in that reaches HR at once, the payroll, a payslip and a Christmas vacancy.
A four and a half minute film follows the books of Northbank Trading, an invented wholesaler: what is owed both ways, a payment recorded against an invoice, supplier bills settled, cash flow weeks ahead, and an income statement read from the ledger.
A four minute film follows Granite and Grain, an invented furniture workshop: one register of everything it owns, the cover on each thing, the lease and its dates, and a fault that cannot go to an electrician whose insurance has lapsed.
A three and a half minute film follows Kilnside Builders, an invented building firm with seven vehicles: a board of what is legal to go out, a tipper kept in by lapsed insurance, and a lorry check-out refused because the licence does not cover it.
A five minute film follows Granite and Grain, an invented furniture maker, as a work order is released with its bill pinned and its standard cost known, Planning shows the finishing room over its hours, and Quality and Maintenance keep the line honest.
A five minute film walks through the public Rutba Sign site as a person holding a document would: the guides on what can be signed electronically and what makes a signature hold up, then a drafting wizard that starts from the place a document is for.
Forty-nine how-to films for Rutba Office are now on YouTube and on office.rutba.io, each three to five minutes on one task, from merging PDFs to Presenter View, each recorded in the released app on files made up for the film.
Sixteen short films teach Rutba Office Data Files in order, on one invented corner shop: tables and fields, relationships, queries and SQL, forms and reports, then till receipts, invoices and a mail merge printed from the shop’s own records.
Rutba Data Files, the free database in Rutba Office, comes with a working database for twenty-five kinds of small business, from a takeaway to a landlord. Each has its tables, queries, reports and print templates ready, with a year of invented records or none.
Rutba Vision spreads recording, AI and search over nodes on each site, joins the sites at a hub without moving their footage, and turns AI on camera by camera. This is how it is built, and why the recorder never stops.
In two days Rutba Office grew to thirteen apps and let you choose which ones you keep. Talk brought messages and calls, Worksheets learnt Lotus 1-2-3, dBASE and Access, and Mail’s Out of office now runs at your mail server.
Data Files, the thirteenth app in Rutba Office, keeps related tables in one file, with queries, forms, reports and print templates for invoices, receipts and payslips. Twenty-five sample businesses show it at work, each with a year of invented records.
A Data Files database can now ask who you are and show each person only what their role allows. Its tables can live in PostgreSQL, MySQL or MariaDB, be kept as a copy that works offline, or be read from a CSV file, a spreadsheet or a web address.
Rutba Office 2.18 puts right what the how-to films found. Documents gains Modify Style, comments tied to their words and tracked changes reviewed one by one. Worksheets gains filter arrows, charts that follow their cells and PivotTable filters.
Rutba Office 2.20 installs only the apps you tick and adds the rest later as signed packs. Profiles keep people or kinds of work apart on one computer, Mail now makes its changes at the server, and Strict Open XML files open and save.
Rutba Office 2.21 opens many more kinds of picture: TIFF a page at a time, Photoshop documents, EMF and WMF drawings, and HEIC and camera RAW through codecs Windows already has. Remove location takes the place out of a photo and keeps the rest.
Rutba Recorder records your screen, camera and voice as one finished video, from scenes you can change while it records, and Go Live streams it to YouTube, Facebook, Twitch or any RTMP server at once. Video now plays a file before you edit it.
Rutba Office is a free, open-source office suite for Windows: thirteen apps in one download, from documents and spreadsheets to PDFs, mail, databases and live streaming. It works offline, needs no account except for Talk, and is free for home and business.
Version 1.51 turns receipts into spreadsheet rows, shows an attached invoice’s total in Mail and makes a scanned form’s tick boxes into real check boxes. It reads six languages on your own computer, and a page’s own sums decide which figures go in unchecked.
Rutba Office went from 1.0.0 to 1.51 in five and a half weeks, and from seven apps and 577 tests to ten apps and 2,576. Numbers past fifty had stopped saying anything, so the next release is 2.0: a new number for the same free beta.
Rutba Office 2.0, released on 15 October, finishes the review tools: Presentations and Worksheets now redact and inspect a file as Documents does, a slide show can be drawn on, and the dark theme was measured for readable text in every app.
Video now writes its own MP4 with the computer’s hardware, about twice as fast as real time. Image keeps selections and types on the picture. And every app passes an accessibility audit and works from the keyboard, with a screen reader and in High Contrast.
Rutba Office 1.46 to 1.49 added an app for PDFs. It reorders, splits and merges pages without redrawing them, makes scans searchable, fills forms, places a signature, and redacts by taking the words out of the file itself.
Since 1.47 Rutba Office reads the words in scans and pictures itself, with the network off, in English, Urdu, Arabic, Hindi, Chinese and Japanese. Scanned PDFs become searchable, a photo’s words can be copied, and a printed table lands in cells.
Rutba Office Mail opens Outlook .pst, .ost and .olm files and mbox archives without importing them, searches them all at once with the syntax people already know, and exports what it finds with a SHA-256 manifest for legal hold.
In September Rutba Office had 257 buttons that did nothing yet. Since 1.49 it has none: most were built, and the ones that only work with an online service were taken out. 1.48 redrew every ribbon, and 1.50 added forms, redaction and Compare to the editors.
On 11 October two testers used the live apps as staff and customers do. They found two blockers and over a dozen serious faults, from a till that misread refunds to a cash-on-delivery order shown as paid. Nearly all were fixed and released on 13 October.
Every Rutba suite app used to be built and shipped as an image of its own: 46 builds, 38 minutes and 4.1 GB of nearly identical copies. Since 13 October they compile into one image in under twelve minutes and run in 14 containers instead of 46.
Video now records your screen with your camera in the corner and builds introduction videos scene by scene, with a teleprompter and captions. Image gains layers, selections, masks and a healing brush, and a document’s pictures can be edited there.
A shop that sells at a counter and online, delivers some orders itself and has a bookkeeper uses five Rutba products. They work as one business because they share one product list, one stock number, one order and one customer.
When a signed agreement is disputed, nobody argues about the picture of the signature. They argue about who signed, what they saw, when, and whether the document has changed since. Here is what a good evidence record holds, and what to ask any provider.
Between 9 and 10 October Rutba Office finished its Urdu, added Arabic and Hindi, and learnt what each language needs beyond its words: Hijri dates, Arabic and Devanagari digits, a Find that ignores vowel marks, and Arabic justification in print.
Video becomes an editor with clips, sound, transitions and titles on a timeline. Image gains quick edits and tone tools, Pictures edits a whole folder at once, and Documents lays its pages side by side as Word does, with Ctrl and the wheel to zoom.
Since Rutba Office 1.29.0 the word processor is called Documents and the slides app Presentations, so their names match Worksheets, Contacts and Pictures. Pinned icons, default apps and file icons carry on working after the update.
Between 6 and 8 October Rutba Office went from 1.28.0 to 1.29.10. Old Office files open in full, Worksheets has Power Query and scripts, Presentations records narration and video, and Calendar syncs with a server you choose.
Rutba Office 1.29.5 opens Word documents back to Word 1.0, Write and DOS Word, Excel workbooks back to Excel 2.1 and PowerPoint 97 to 2003 decks with their layout kept. Since 1.29.6 the ones with a password open too.
Worksheets in Rutba Office 1.29 shapes data in a Power Query editor, runs scripts written like Office Scripts in a sandbox that cannot reach the network, and calculates LAMBDA, XMATCH and the array functions Excel 365 added.
The slides app in Rutba Office 1.29 plays video and audio, records a narration per slide, exports the deck as a video, shows your camera live in a Cameo, and moves shapes along motion paths that PowerPoint plays as its own.
The word processor in Rutba Office 1.29 records formatting, sorts and paragraph marks under Track Changes, compares a document with an older version, and has Word’s Table Design and Table Layout tabs, with formulas in cells.
Since 1.29.4 a right-to-left paragraph runs from the right margin in Documents. By 1.29.10 it reached tables, sheets, slides and the PDF, where Arabic letters join, Urdu keeps its own forms and the words still copy out as text.
Rutba Office 1.29.8 keeps Calendar and Contacts in step with a CalDAV or CardDAV server such as iCloud or your own. Mail files junk with a filter that learns from what you mark, without sending a message anywhere to decide.
Design Ideas, the thesaurus, the junk filter, worksheet scripts and 3D models arrived in Rutba Office in October. Each one runs on the computer the file is on. Here is how, and what does still go over the network.
Five releases of Rutba Office went out on 9 October. 1.30 put right what a careful reading of 1.26 to 1.29.10 found, and 1.31 to 1.34 added WordArt that bends, templates of your own, recording with the camera and Word’s multilevel lists.
Four more releases on 9 October. 1.38 puts every window of Rutba Office into Urdu with its frame right to left, 1.37 moves the work on documents off the process every window shares, and 1.35 and 1.36 add Power Query steps and Word’s own lists.
Since 6 October all 46 apps in the Rutba suite run in production, each at its own address under rutba.io, such as pos.rutba.io or books.rutba.io. Your sign-in says whose data you see, so no business needs addresses of its own.
The Affiliate Program’s money half was built on 8 October. Codes and referral links work at the web checkout and at the till. A manager signs off each earning after the return window, and an administrator approves each payout. No shop has switched it on yet.
From the next release, Rutba tells each organisation’s instance which apps it may install. The launcher in every app follows that list, and the console’s Modules page says, app by app, whether it is installed and who decided.
Rutba Office 1.26, 1.27 and 1.28 open password-protected Office files, run a mail merge with envelopes and labels, record tracked changes as you type and put a theme on a workbook, and 1.28 fixes a window that stayed hidden after updating.
From 26 September, staff reset their password at Rutba’s sign-in and a shop’s customers reset at the shop, never across. Somebody only their company’s workspace knows can now reset at Rutba too, and every address still gets the same answer.
A till that adds up its own refund can pay out more than the sale took. Returns and exchanges are now priced on the server from the original sale, and at the order desk the person who collected the cash no longer confirms it.
On 26 September we checked the catalogue, the comparison pages and the blog against what the apps actually do. Some pages called built apps unbuilt; others sold features that do not exist. Both kinds are corrected, and dated.
Since 24 September, Rutba’s workspaces no longer ask for a password of their own. You sign in once, the organisation you chose stays chosen until you switch, nothing about it travels in a link, and signing out anywhere signs you out everywhere.
One sign-in works by small hidden pages that tell an app who is signed in. The first version trusted any address ending in our domains, which included shops running their merchants’ own code. Review caught it before it reached production.
Rutba’s sign-in kept its own database: sessions, keys, second-factor challenges, an audit trail, and a second copy of everybody. Since 21 September it keeps nothing. Every record it needs lives in the one backend that already held people.
A landlord who signs three leases a year and an office that sends forty agreements a month do not need the same plan. Rutba Sign now has four rungs, the first five envelopes each month are free, and every rung costs less an envelope than the one below it.
Eleven releases of Rutba Office in two days, and most of what they did to Rutba Word happened on the page itself: footnotes at the foot of it, borders round it, a watermark behind it, and a sheet of scanned cards that finally prints as it looks.
The same eleven releases turned Rutba Office’s spreadsheet and slides from viewers that could edit into tools you can build with: sheets from the tabs, tables, sorting and tracing in Worksheets; the Format Painter, footers and find-and-replace in Presentation.
The content backend Rutba runs on ships with no second factor for its admin panel, so an administrator’s password was the whole of the lock. We built one, put it in front of our own panel, and published it for anybody running the same backend.
Thirty-one releases between 8 and 21 September closed most of the list we wrote on day two. Here is that list read back: what is in an installer, what is only in the source, what is still open, and who should not switch yet.
Rutba Office’s picture viewer crawled on a real folder: every tile decoded a whole file, every clip was a running player, and moving on emptied the screen before the next picture arrived. All four causes are gone in 1.14.
Rutba Word has wrapped words round a floating picture since 1.11, and then printed it as a block under the paragraph, which is the kind of difference that is only discovered at a printer. In 1.15 the page prints what the screen shows.
Sign in at Rutba and the first thing that happens is a lookup on your address, not a password box. It reads only the domain, so it answers the same for an address that does not exist. And it was quietly doing nothing for weeks before we noticed.
Turning on two-factor used to mean typing a thirty-two character secret by hand. It is a code you scan now, or a button on a phone, and the factor itself lives in one store rather than two, which is the part that keeps a settings page honest.
A sign-in that looked like a wrong password was a security header doing its job too well: it allowed the form but not the page the form lands on. The fix was to build that rule from the list of places a sign-in is already allowed to end.
Signing in used to send everybody to the customer console, including people who hold no customer account. It now sends you to the one app you can actually open, and when you hold several, a page lays them out by organisation, with a link on every one.
Every Rutba deployment now tells us what it is running, and gets back what it is licensed to run. Nothing is refused by that answer: drift is recorded, said out loud and billed if somebody chooses, never turned into an outage you did not plan.
Nobody hand-links a marketing site consistently, and a site with no internal links makes readers use a search engine to find its own pages. So the prose is structured content now, and the first mention of a product in any sentence becomes a link.
Per user was the wrong unit for a shop, not the wrong amount: a three-person counter paid three times for one till. Commerce, Inventory and Orders are now bought by the business on the orders it takes, with every member of staff and every register included.
One product was advertised at three different prices depending on which Rutba site you opened, and nothing could tell. Every figure now comes from one record as the page renders, and a test fails the build if anybody types a price into the site.
Our sign-up refused a short list of common passwords, exactly as written. Nobody types them exactly: they add a year, a row of digits or a symbol. The check now finds the word underneath, and leaves passphrases alone.
Rutba Assistant answers questions about your business from inside whichever app you are in. It signs in as nobody: every call it makes carries your sign-in and meets the checks the screen would, so it never sees or does more than you.
An answer with a source can be checked; an answer without one can only be trusted. Under every Rutba Assistant answer are the API calls it made, assembled from what actually ran, never from what the model says it did.
Press Report instead of Ask and Rutba Assistant writes a spreadsheet into your own Drive, with a native chart and a Sources sheet. The model chooses the layout; every figure is carried across from the recorded responses.
“Your organization is not licensed for Payroll” is a question for whoever buys. “You do not have access” is one for an administrator. A route that is not there is a bug for us. Rutba Assistant keeps those apart.
The panel only reads. When you want Rutba Assistant to do something, it becomes a plan: every step written out with the exact request it will send, approved by a person, run by a worker, and stopped the moment a step fails.
If your team already works with an AI assistant, it can work with Rutba through the Model Context Protocol, on your organization’s own key. It gets six tools, meets the same three checks, and can propose a change but never make one.
A credit controller wants the worst debts first. A finance lead wants to know whether Friday’s supplier run leaves enough in the bank. What Rutba Assistant reads in Rutba Books to answer each, and where it stops.
A store manager asks what will run out before the supplier comes, what expires this month, and whether the last order was billed at the contract price. What Rutba Assistant reads to answer, and why a cashier asking the same gets less.
A supervisor, an HR manager and an employee ask about people. Rutba Assistant answers each from the calls the People screens make, and because it asks as the person, one question returns a team, a company or one person’s own record.
A salesperson asks whose follow-up is most overdue, a support lead asks why a ticket was never picked up, and a shop manager asks why a till was short at close. What Rutba Assistant reads to answer each one.
A dispatcher at six in the morning needs three answers before the first van goes: what is due and unassigned, which vehicles are legal to drive, and which drivers are near their hours. What Rutba Assistant reads to answer each.
A production manager, a planner and a quality lead ask the factory three hard questions: where the time is going, whether next week’s plan will hold, and which finished goods contain a supplier’s bad lot. What Rutba Assistant reads to answer.
A marketing manager asks what went wrong with last week’s send, how many real people a segment contains, and what the catalogue gained this month. What Rutba Assistant reads to answer, and why pressing send stays with a person.
Somebody back from leave asks what they missed, where a decision about an order was made, and why a new phone number will not ring. What Rutba Assistant reads across mail, chat and calls to answer, only in the conversations they are part of.
An operations manager asks what falls due in the next ninety days, which software licences are over-allocated, and what a leaver has not handed back. What Rutba Assistant reads across Facilities and Assets to answer, including what it cannot count yet.
A director asks what is waiting for them to sign, what the business has sent a customer and where each agreement stands, and whether a stamp or a notary is needed in the other party’s country. What Rutba Assistant reads in Sign and Workspace to answer.
Rutba Relay now counts the deliveries each organization started in the last hour. Just over its ceiling, a publish is told to wait ten minutes. Four times over is not a person, and that organization’s publishing is paused until somebody looks.
Rutba Office has installed its own updates when you quit since version 1.7, and said so only on the launcher. From 1.13 a release is announced in every window the moment it is found, and each release is proved by watching the last one update itself.
Rutba Word lays a document out on pages as you type, and since 1.12 its ruler is a control rather than a picture: drag an indent, a tab stop, a margin or a table column, and the file is written the way Word writes it.
Some agreements need more than signatures before a court will look at them. The formality is declared on the agreement and has to be satisfied before it is sent or sealed. Arrange it yourself for free, or have a person at Rutba arrange it at cost.
Reading .odt, .ods and .odp but saving them as something else is half a promise. Rutba Office now writes OpenDocument too, so a file that arrives in an open format leaves in one.
Running a publishing service means staff sometimes need to look inside a customer’s workspace. What they see is who is in it, what is connected and how recent posts went. Never a credential, and never a word of a post.
We publish every customer price, to the cent. The one number our partner site deliberately leaves out is the partner margin, because a margin that works in one market is unsellable in the next, and a published one would be wrong in ten of eleven territories.
The promoter’s page on the storefront is deliberately thin: it says where you stand, and nothing else. A dashboard of zero earnings would tell an approved promoter they have earned nothing, a different and much worse statement than "this does not exist yet".
A product page named its apps in a sentence each, which cannot tell you whether a till handles returns. Forty apps now have a page of their own, listing every screen in them (read from each app’s own menu) with screenshots of it running.
In an agreement with five parties, the first to sign may wait weeks for the last. Until now they held nothing for it. Each party now leaves with proof of their own act, countersigned by Rutba the moment they acted.
A document engine tested against files its own authors made is tested against their understanding of the format. So our fixtures are written by Excel, Word and PowerPoint themselves, and the first run found four things we had wrong.
When a social network changes something overnight, a publishing service can fire thousands of failing requests at it and collect strikes against your accounts. The Relay’s switches stop that, and every one records who threw it and when it clears.
The fear that stops most businesses reselling software is being undercut by the vendor they represent. So who owns the customer is decided per track, deals are registered from day one, and you are told which accounts are already ours before you sign.
An individual, a creator with an audience, a registered business and a member of the shop’s own staff carry different obligations. A company accepting an individual’s terms is not bound by them, so the affiliate programme keeps one agreement per kind.
A Rutba storefront used to fire analytics and the Meta pixel on the first page view, in every country, with no notice. Now it asks first where the law expects it, and a shop that runs its own consent tool can take the whole decision over.
A flatshare agreement that is not a tenancy, a letter of authority that is not a power of attorney, and wills last of all and on paper. Where a document generator draws its lines says more about it than what it generates.
Adding a mail account used to mean an IMAP host, an SMTP host, two ports and two encryption settings: a form most people cannot fill in about their own mailbox. All of it is knowable, so Rutba Office works it out.
The Relay used to run its own sign-up, passwords, second factor and invitations. Now a person signs in once with their Rutba account, and their organisation gives them the Relay the way it gives them anything else.
The first part is eight fields and two minutes. The second asks for turnover, headcount and a year-one commitment, and nobody should have to hand those to a vendor they have not yet decided about.
A shop paying people who send it customers looks like a marketing feature. It is really money owed to outsiders, cleared against returns and posted to the books. So we built the sign-up first, and the money half waits on three decisions rather than on guesses.
A bare product link previews as a catalogue picture and a line of copy. So when a shopper shares a product from a Rutba storefront, it shares the brand’s latest post about it (campaign photography, caption and all) with the product one tap below.
"The login page is broken" describes several pages on several deployments. So every page now ends with a short reference (which deployment, which page, which build and which visit) that a screenshot is enough to trace, and that never carries your data.
Eleven everyday agreements, fifteen jurisdictions, and a rule we hold to: a guided document is not a template. It asks what is true, composes the agreement from the answers, and arrives with its parties and fields already in place.
The free suite is nine applications now. Calendar reads and writes .ics, Contacts reads .vcf and CSV, an invitation is accepted from inside the message it arrived in, and addresses complete from your own book.
An accountant who keeps being asked what to replace a bookkeeping stack with and a country distributor running a whole territory want different things from a vendor. So the partner programme has four tracks, not one with tiers.
A point of sale that trusts the total its screen sends is fine until a discount means money owed to somebody else. Our till now asks for a sale to exist, and the server says what it costs, the rule the web checkout has always followed.
Six Rutba sites used to disagree about whether you were signed in, and two of them collected passwords of their own. Now there is one front door, and since 24 September it is the one sign-in for the whole suite, the workspaces included.
Signature software treats the signature as the finish line. For the business that sent it, that is the moment an agreement starts costing attention: renewals, notices, formalities, and proof somebody asks for years later.
Nine desktop applications, our own document engine, and the Outlook archive formats almost nothing else opens. Free under the AGPL, no account, no telemetry. And a commercial reason it is not charity.
Software is full of places where the arithmetic is not exact. Each one is a decision about who absorbs the fraction, and we made that decision once, in advance, for all of them.
When two systems can both price the same thing, eventually both of them do. Here is the single rule we hold to instead, and the one line of SQL that enforces it.
The strongest privacy claim software can make is not a policy. It is that you can pull the cable and nothing breaks. Here is what that takes, and the one exception we will not pretend does not exist.
Pipeline stages are the easy half of a CRM and every product has them. The half that decides whether anyone can answer the phone is whether the call, the mail, the ticket and the order hang off the same customer.
A till sale, a pay run and a stock revaluation are all journal entries that somebody currently types twice. We made each of them post its own, and what is left is the work actually worth doing.
The argument always starts the same way: two systems each keeping their own copy. The fix is not better syncing. It is deciding, once, which one is allowed to hold the number.
What decides a dispute two years later is whether you can still show what happened: who opened it, from where, what they accepted, in what order, and that not one byte has moved since. That record is the product.
Not in the employee record and not in the pay calculation. In the gap between them, where somebody types hours from one system into another. We removed the gap, and left the biometrics out on purpose.
Which is worth exactly as much as your relationship with that vendor. Ours returns a record anyone can check independently: from a public endpoint, with no key, that does not reach your systems at all.
So that place should not be three separate queues. Web, marketplace and phone orders are the same object the moment they exist, which is the decision that makes a picking list, a driver app and a return all work the same way.
Most production planning goes wrong in the gap between them. An MRP run that reads today’s stock, plans against a pinned bill version, and hands the dispatch list to the bench closes that gap, and works offline when the bench has no signal.
Running a site on one system and a till on another means two product lists, two price changes, and a stock number that is wrong in at least one place. Web and counter are two channels of one business, so we built them that way.
Bounces, complaints and the slow drift into spam folders are a reputation problem, and reputation is a property of your domain rather than of any one product. So transactional mail and campaigns go out through the same relay.
The HR list of issued kit, the fixed-asset register in accounting, and whatever the plant keeps for machines. They describe the same laptops and the same machines, and the auditor asks all three.
That is the commodity half. The half worth building is an inbox that knows your business: a message from a customer filed against the person, contact, customer or order it concerns, and a To box that knows your CRM contacts.
The export was correct on the morning somebody ran it. Then stock moved, invoices were paid, and the file kept looking authoritative. Binding a cell to live data is a smaller idea than it sounds, and it fixes the whole class.
The scheduling half is well served. The part that is not: a documented API the console itself is built on, so anything else (including an assistant with the same permissions a person has) can publish the same way.
Six months later, the reason you discounted that order is in a channel, ninety messages up, phrased in a way nobody would search for. Some conversations belong in a channel. That one belongs on the order.
It is also how storage bills grow. Keep one master and generate whatever dimensions are asked for at request time, and a redesign that changes every image size costs a URL change rather than a re-upload.
A prospect and a ten-year client get identical copy, because the segment was built from a CSV somebody exported in March. Segments from live records are not a nicer feature. They are a different product.
Cloud camera services charge monthly to store your footage on someone else’s disk, and stop working the moment the line drops. Rutba Vision runs on a box in your building. The only thing that talks to us is a licence check.
Rooms, lobby, breakouts, polls, whiteboard, attendance reports: built and tested. The media server all of it talks to is not deployed, so the product is listed as coming soon. Also: why we refuse end-to-end encryption.
The ad is not wrong when it is made. It becomes wrong on the Tuesday somebody edits the catalogue, and nothing about the file says so. Rendering one template once per row of a product sheet makes the fix a re-run rather than forty edits.
So we built the record-keeping half first and the telephony second. That is backwards from how phone systems are usually built, and it means you cannot buy this yet, but the half that exists is the half that was missing.
Folders, versions, sharing, quotas and a published SDK all work today, as the layer underneath Rutba Docs. The standalone interface is not built, so the product is marked coming soon rather than early access.
Most partner programmes offer a territory that three other partners are already working. Ours has eleven regions and none of them is spoken for, which is a statement about how early we are, not how generous.
What is due, what is off the road, what did fuel cost per kilometre. Those are asset questions, so the vehicle goes on the asset register rather than in a fleet system’s own copy of it. We published the design first; the app has since been built.
Follow along: RSS · what we shipped
One family
One account across all of it. Sign in once and the products know each other.
Rutba Sign
sign.rutba.io
Send a document for signature. Verification is free, forever.
Rutba Relay
relay.rutba.io
One API to publish a post to many social platforms, with every delivery reported.
Rutba Office
office.rutba.io
Documents, sheets and slides on your own desktop.
Rutba Partners
partners.rutba.io
Resell, implement and build on the platform.
PORTAL-BLOG · 2e7a24c
